[Bug 257212] net-im/prosody rc script not creating pidfile; effectively breaking service control
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 257212] net-im/prosody rc script not creating pidfile; effectively breaking service control"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 257212] net-im/prosody rc script not creating pidfile; effectively breaking service control"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 257212] net-im/prosody: Fails to start under RC, does not creat pidfile"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 257212] net-im/prosody: Fails to start under RC, does not creat pidfile"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 257212] net-im/prosody: Fails to start under RC, does not creat pidfile"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 257212] net-im/prosody: Fails to start under RC, does not creat pidfile"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 257212] net-im/prosody: Fails to start under RC, does not creat pidfile"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 257212] net-im/prosody: Fails to start under RC, does not create pidfile"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 257212] net-im/prosody: Fails to start under RC, does not create pidfile"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 257212] net-im/prosody: Fails to start under RC, does not create pidfile"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 257212] net-im/prosody: Fails to start under RC, does not create pidfile"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 257212] net-im/prosody: Fails to start under RC, does not create pidfile"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 15 Jul 2021 19:48:32 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257212
Bug ID: 257212
Summary: net-im/prosody rc script not creating pidfile;
effectively breaking service control
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs@FreeBSD.org
Reporter: phryk-ports@wzff.de
CC: thomas@beingboiled.info
CC: thomas@beingboiled.info
Flags: maintainer-feedback?(thomas@beingboiled.info)
Doing `service prosody start` will start prosody, but not create the PIDfile
the rc script expects.
This leads to `service prosody status“ claiming the service isn't running when
it actually is and keeps `service prosody stop` from ever working, meaning it
has to be stopped by manually using `kill` on it.
--
You are receiving this mail because:
You are the assignee for the bug.