| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
option is specified. This behavior is documented on the manual page.
PR: bin/187265
Submitted by: Kimo R
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
2. Write the supervisor pid before the restart loop, so we don't
uselessly rewrite it after every child restart.
3. Remove duplicate ppfh and pfh initialization.
Approved by: re (glebius)
MFC after: 2 weeks
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
|
|
|
|
|
|
| |
that daemon can be used w/ rc.subr and ports can use the additional
functionality, such as keeping the ldap daemon up and running, and have
the proper program to signal to exit..
PR: bin/181341
Submitted by: feld
Approved by: re (glebius)
|
|
|
|
|
|
| |
GNU/Linux *duck*.
MFC after: 1 week
|
|
|
|
|
| |
Submitted by: Andrey Zonov <andrey zonov.org>
MFC after: 3 days
|
|
|
|
|
| |
Submitted by: Andrey Zonov <andrey zonov.org>
MFC after: 1 week
|
|
|
|
|
| |
Suggested by: Andrey Zonov <andrey zonov org>
MFC after: 2 weeks
|
|
|
|
|
| |
Suggested by: Andrey Zonov <andrey zonov org>
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
| |
process. Normally it will cause the child to exit followed by the
termination of the supervisor after removing the pidfile.
This looks like desirable behavior, because termination of a
supervisor usually supposes termination of its charge. Also it will
fix the issue with stale pid files after reboot due to init kills a
supervisor before its child exits.
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
not to leak the descriptor after exec(3). This raises the issue for
daemon(3) of the pidfile lock to be lost when the child process
executes.
To solve this and also to have the pidfile cleaned up when the program
exits, if a pidfile is specified, spawn a child to exec the command
and wait in the parent keeping the pidfile locked until the child
process exits and remove the file.
Reported by: Andrey Zonov <andrey zonov org>
Suggested by: pjd
Reviewed by: pjd
MFC after: 2 weeks
|
|
|
|
|
|
| |
for pre-creating the pidfile with appropriate owner and permissions.
Requested by dougb
|
|
|
|
|
|
| |
better to leave the pidfile open where it was. Add a note to the
man page describing pidfile strategies to use if the daemon is to
be run as a user other than root.
|
|
|
|
|
|
|
|
|
|
| |
so pid files can be written in /var/run when started as root.
I do not expect this to cause any security issues, but if anyone objects
it could be easily reverted.
PR: bin/159568
MFC after: 4 weeks
|
| |
|
| |
|
|
|
|
| |
The stray ':' was from the defunct '-g' group arg.
|
|
|
|
|
|
| |
option. Bump doc date for manual page changes.
Reviewed by: rwatson, ru, will (older version)
|
|
|
|
| |
commit because it was not part of the new code.
|
|
|
|
|
|
| |
PR: 108523
Submitted by: Dmitri Alenitchev <dmitri@dworlds.ru> (original version)
Reviewed by: mpp (first reply to PR)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
does not know anything about the pid-file and we don't keep a babysitting
process for the task, the pid-file will linger.
Submitted by: mi
PR: 56398
|
| |
|
| |
|
| |
|
| |
|
|
controlling terminal.
Discussed on: -hackers
Obtained from: BSD/OS
|