Hi,
We are using Upstart version 0.5.0.
If a job has a respawn stanza and the main process terminates before
post-start script ends, there is a assertion which is causing a kernel
panic.
This does not cause a assertion if the respawn stanza is not present.
I am working on a fix for this issue.
Hi,
Would using inotifywait with a timeout and wait for dbus-daemon to
create the pid file work?
dbus-daemon by default creates the pid in /var/run/messagebus.pid (I
believe this path is configurable when launching dbus-daemon)
This may not work if dbus-daemon is crashing after the pid file is
Hi,
I have a situation where I have to start a job (foo) when any job on the
system stops except itself.
How do I write the start on condition for this?
I tried
start on stopped JOB!=foo
but it does not work (job does not get started if any other job stops).
If I remove the JOB!=foo condition, it
:27 PM
To: Sandeep Puddupakkam (spuddupa)
Cc: upstart-devel@lists.ubuntu.com
Subject: Re: How to add not equals in start on condition for a job
On Tue, 2010-04-20 at 13:40 -0700, Sandeep Puddupakkam (spuddupa) wrote:
I have a situation where I have to start a job (foo) when any job on
the
system
Hi,
I have 2 jobs
foo
env NAME=foo
export NAME
console output
script
echo INSIDE [$UPSTART_JOB]. NAME:[$NAME]
exec sleep 500
end script
foo1
-
start on started foo
env NAME=foo1
export NAME
console output
script
echo INSIDE [$UPSTART_JOB]. NAME:[$NAME]
end script
When I start
