[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: restarting ffmpeg process

From: Martin Pala
Subject: Re: restarting ffmpeg process
Date: Wed, 7 May 2014 16:57:19 +0200

Alternatively you can monitor the process using pattern (no pidfile needed):

check process myprocess matching "/usr/bin/myprocess -a -b -c"


On 07 May 2014, at 13:34, Anthony Griffiths <address@hidden> wrote:

I think I realise now what the (simple) problem is.
monit does not line '/bin/sh /root/', I need to use something else but I don't know what.

On Wed, May 7, 2014 at 7:09 AM, Weedy <address@hidden> wrote:
On 06/05/14 06:03 PM, Anthony Griffiths wrote:
> I wrote a script called that follows your instructions
> but even though ffmpeg starts fine it does not create a pid file. I
> created this:
> *long-ffmpeg-command &*
> *pid=$!*
> *echo $pid > /var/run/*
cat > /root/
if [ ! -d /var/run/ ]; then mkdir -p /var/run/; fi
if [ -f /var/run/ ]; then rm /var/run/; fi

/usr/bin/ffmpeg -a -lot -of -options &
sleep 3 # make sure it's given enough time to start/die??
echo $(pidof --single-shot ffmpeg) > /var/run/

<hit ctrl+d after at least one blank line>
chmod +x /root/ # not really needed
> but this didn't work and and after trawling google and trying a few
> variations the script still does not create a pid file.
> in monitrc I have:
> *check process stream with pidfile /var/run/*
> *       start = "/usr/bin /root/"*
> and monit starts without any complaints

I... what? /usr/bin is a directory. This is probably why $! failed for
you, your not running the file with a specific interpreter. Hard code
the interpreter so this never happens again.

start = "/bin/sh /root/"

To unsubscribe:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]