|
Size: 814
Comment:
|
← Revision 3 as of 2013-01-14 09:22:09 ⇥
Size: 862
Comment: cat / needs work
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| The {{{runit}}} package also needs to disable this behavior, so they've collected a lot of hints [http://smarden.org/runit/runscripts.html here]. | The {{{runit}}} package also needs to disable this behavior, so they've collected a lot of hints [[http://smarden.org/runit/runscripts.html|here]]. |
| Line 20: | Line 20: |
| ---- CategoryNeedsWork CategoryMemberManual |
Many daemons "auto-background" themselves.
Technically this is accomplished by having the daemon call setsid(), then fork() and then having the parent exit(). The result is that the child is re-parented to process 1 (init) and is in its own "session group".
Unfortunately this means that a daemon started via k5start which does this is no longer a child of k5start; this means that k5start cannot do its job.
Here are some hints on how to get various daemons to disable this behavior:
1. general
The runit package also needs to disable this behavior, so they've collected a lot of hints here.
2. eggdrop
Pass in the -n argument
3. apache2
Pass in the -DFOREGROUND argument