On Fri, Sep 2, 2011 at 7:06 AM, mmaiza <[email protected]> wrote: > While I was reading the current code I noticed that -d is no longer > available as well the functions deamonize, dfork. Does this mean that > you no longer intend to support this feature?
This has been mentioned a couple of times before on this mailing list. There are better ways to accomplish the same thing, using other tools (such as init, Upstart, systemd, launchd, runit, daemontools, SMF, supervisord, etc, etc, etc). >From now on, beanstalkd won't encourage the antipattern of having individual daemon processes fork themselves to detach from the parent process. >From http://dustin.github.com/2010/02/28/running-processes.html: > Self-daemonizing programs start you down the path to > hell. You can’t use any sane keepalive techniques so > you have to resort to polling process lists or > checking the pid or something. Even managing that > pidfile gets hard when you combine it with things > that change their own uid for safety (because you > should never run anything as root). See https://github.com/kr/beanstalkd/tree/master/adm for specific instructions on how to run beanstalkd. kr -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
