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 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 goes into an infinite loop as expected (foo gets started every time foo job stops) This should work with 0.6.5 Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist? signature.asc Description: This is a digitally signed message part -- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
Re: How to add not equals in start on condition for a job
At 4:40pm -0400 Tue, 20 Apr 2010, Sandeep Puddupakkam wrote: I have a situation where I have to start a job (foo) when any job on the system stops except itself. How do I ... Quick educational opportunity: Sandeep, the next time you send a message to the list -- to *any* list --, if it's not in reply to a particular message, the please create a new message. I don't know what client you use, but that would be New, Compose or Write. If you don't, and use a Reply button instead, then you mess up the threading of the messages. While you have a goal to get your questions answered, the list archives are there for others to come after and learn. When you hit reply and just change the subject, you leave certain information in the context of the message. Specifically, this line (in the header), which shouldn't be there: In-Reply-To: 364299f40902231849t30b10318k14f4634e5afaf...@mail.gmail.com Which says that you hit reply while selecting Garrett Cooper's message from over a year ago (23 Feb 2009). Regards, Kevin -- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
RE: How to add not equals in start on condition for a job
Scott, We are using 0.5 + a few patches. I should have mentioned that in my previous email. I was looking in the release notes for 0.6.5 and see that this is fixed using 513035. How do I get the patch for this fix so that I can apply it to 0.5 that we are using? Usually the diffs are attached to the Bug. Don't see them in this one. https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/513035 I can download 0.6.5 and look for the diffs. Is there an easier way? Thanks, Sandeep -Original Message- From: Scott James Remnant [mailto:sc...@netsplit.com] Sent: Tuesday, April 20, 2010 2: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 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 goes into an infinite loop as expected (foo gets started every time foo job stops) This should work with 0.6.5 Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist? -- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
