[07:28] <mikedlr> hi;  I have an init script run from upstart;  I'
[07:28] <mikedlr> I am trying to get it to kill a service, but it doesn't get run.
[07:29] <mikedlr> This is on RHEL6;  The script is installed as /etc/rc4.d/K***.  Can anyone suggest why it is ignored?
[07:30] <mikedlr> when I switch into runlevel 3 where it is linked as /etc/rc3.d/S*** then it gets run.
[07:39] <jodh> mikedlr: does it get run as /etc/rc3.d/K***? Does anything else run in runlevel 4?
[07:41] <pw12> hi, I was wandering: what's the state of the cron event support for upstart?
[07:42] <mikedlr> jodh;  I have it running as S99xx in runlevel 3.  Then it runs
[07:42] <jodh> pw12: scott has a branch, but it hasn't been looked at for a while due to other priorities. Patches always welcome of course! ;)
[07:42] <mikedlr> service xxx status shows running.
[07:46] <jodh> mikedlr: ok, but can you answer my 2 questions?
[07:47] <mikedlr> jodh;  it seems quite a few kill scripts run as I switch into runlevel 4.  
[07:48] <mikedlr> jodh; the other software that was already running but doesn't have a kill script seems to stay there. 
[07:48] <jodh> mikedlr: it doesn't sound like an Upstart issue then. Are you sure it isn't running? Try adding some log calls to the script to be sure.
[07:49] <mikedlr> I put an echo at the start of the script.  
[07:50] <mikedlr> echo eucalyptus-cloud run as $0 with arguments "$@" >> /tmp/cloudrcrun.log
[07:51] <mikedlr> I see "eucalyptus-cloud run as /etc/init.d/eucalyptus-cloud with arguments status" often (even when I don't run it)
[07:51] <mikedlr> I see "eucalyptus-cloud run as /etc/rc3.d/S99eucalyptus-cloud with arguments start"
[07:51] <mikedlr> when I switch to runlevel 3
[07:51] <mikedlr> I see nothing when I switch to runlevel 4.  
[07:54] <mikedlr> yes; jodh; I can confirm that I see "snmpd", for example, working in both directions but I only see eucalyptus in the one direction. 
[08:00] <mikedlr> my expected behavior from upstart is that it runs everything in /etc/rc4.d/K[0-9][0-9]*  in order;  is there some config file which I could expect to change this?  This should be a more or less stock RHEL6 install.
[08:03] <jodh> mikedlr: Upstart doesn't run those scripts: it starts the SysV system which handles that. Is there a lock file somewhere maybe? (/var/lock/*?)
[08:10] <mikedlr> jodh;  there is no lockfile whether I am in level 3 or level 4.  I think that that is probably the cause of the problem.
[08:12] <jodh> mikedlr: ok. I do wonder why it is necessary to create a new service to kill an existing one though. Is a problem with the stop command for the SysV service in question?
[08:12] <mikedlr> jodh;  it's not a new service;  it's the existing script which is not apparently working.. 
[08:13] <jodh> mikedlr: it might be easier to fix that and report it to RedHat then?
[08:24] <mikedlr> jodh - s/redhat/eucalyptus/ - it's already reported :-) thanks.
[16:40] <slangasek> jodh: ok... bug-980917-the-bug-that-would-not-die, landed :)
[16:46] <slangasek> jodh: I think that's ready to be pulled into quantal, then
[17:01] <SpamapS> \o/
[17:30] <jodh> slangasek: thanks!
[20:39] <Almindor> hello
[20:41] <Almindor> how do you define environment variables for a specific user from upstart script? I need to run something as sudo -u some_user but I want some environment vars set on it
[21:19] <gchristensen> hi, where can I find stanza docs for 0.6.5?
[22:32] <SpamapS> gchristensen: man 5 init
[22:33] <SpamapS> gchristensen: http://manpages.ubuntu.com/manpages/lucid/en/man5/init.5.html