On CentOS, added this to the start() function of /etc/init.d/
beanstalkd instead:
echo `ps auxf | grep -v grep | grep "$exec -d $options" | awk '{print
$2}'` > /var/run/beanstalkd.pid
I wonder if this is reliable?
On Aug 9, 3:50 pm, Shiki <[email protected]> wrote:
> Thanks massi.
>
> On Jul 12, 9:53 am, massi <[email protected]> wrote:
>
>
>
> > Hi,
>
> > If you're interested to use a different process monitoring system,
> > here's my experience :
> > I'm monitoring beanstalkd with a ruby process monitoring (bluepill)
> > and it creates the PID for it.
> > The blupill config file I'm using contains :
>
> > Bluepill.application("myapp") do |app|
> > app.process("beanstalkd") do |process|
> > process.start_command = "/etc/init.d/beanstalkd start"
> > process.stop_command = "/etc/init.d/beanstalkd stop"
> > process.pid_file = "/var/run/beanstalkd.pid"
> > process.uid = "beanstalkd"
> > process.gid = "beanstalkd"
> > process.start_grace_time = 15.seconds
> > process.stop_grace_time = 15.seconds
> > process.restart_grace_time = 50.seconds
> > process.checks :cpu_usage, :every => 300.seconds, :below =>
> > 50, :times => 3
> > end
>
> > end
>
> > Hope it helps you :-)
>
> > M.
>
> > On Jul 9, 11:42 pm, Keith Rarick <[email protected]> wrote:
>
> > > 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.
