On Thu, Jul 8, 2010 at 2:56 AM, Shiki <[email protected]> wrote: > If I run beanstalkd like this: > > beanstalkd -d -l 127.0.0.1 -p 11400 > > Where would the pid file be located?
Beanstalkd doesn't create a pid file. The best way to run beanstalkd is without the "-d" option, using a tool such as launchd, upstart, systemd, supervisord, runit, daemontools, or similar. If you really need to create a pid file, for now I suggest running beanstalkd directly (without -d), so that you know its pid. Then you can write the pid to a file. In bash, you can do it this way: $ nohup beanstalkd > beanstalkd.log & $ jobs -p %+ > beanstalkd.pid $ disown %+ However, it's usually better to use one of the tools I listed above. > I noticed that if I run it as "/ > etc/init.d/beanstalkd start", the pid file would be in /var/run/ > beanstalkd.pid. If I run it like the above though, I couldn't find any > created pid file. I think the init script writes a pid file somehow. 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.
