On Sat, Feb 4, 2012 at 6:17 PM, Fred Liangjing Wang <[email protected]> wrote: > I think many users enjoy use this option and some other tools also > used -d option to start a daemon.
This has been discussed here before. For development purposes, one can run beanstalkd in the foreground or use the shell's "&" notation to run in the background. It's just as easy to type "beanstalkd &" as it is to type "beanstalkd -d". For production deployment, popular monitoring tools like launchd, systemd, upstart, supervisord, god, monit, runit, daemontools, etc all work *more reliably* without a flag such as -d in beanstalkd. There are a few examples of how to properly run beanstalkd in production in https://github.com/kr/beanstalkd/tree/master/adm (and I'd really love contributions for other monitoring tools that aren't in that dir yet). Please read http://dustin.github.com/2010/02/28/running-processes.html for a more thorough discussion of how to monitor processes in production. This comes up often enough, maybe I should think about writing a blog post to discuss this specifically in the context of 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.
