[09:05] <vinilios> i created the following upstart conf file http://pastebin.com/2KCd7tNq , run.sh actually runs a java application, while the job starts fine, stop freezes, any idea how to fix it ?
[18:35] <notting> Keybuk: https://bugzilla.redhat.com/show_bug.cgi?id=577709#c5 <- opinions?
[18:36] <Keybuk> notting: that sounds like the old init it still running?
[18:36] <notting> Keybuk: right, it was the equivalent of apt-get dist-upgrade (or whatever) from a 0.3.x system to one that contains 0.6.x
[18:37] <Keybuk> in that dist-upgrade, we restart init
[18:37] <notting> Keybuk: which promptly loses track of all its jobs?
[18:37] <Keybuk> when we were using 0.3, that was just gettys and stuff, which wasn't an issue
[18:40] <notting> hm, would have to run some tests to see how practical that is
[19:02] <sadmac2_> notting: it could work. we might not kill some things like X on shutdown but nothing major.
[19:14] <halfline> gdm is what handles killing X
[19:15] <halfline> of course upstart is what handles killing gdm
[19:15] <sadmac2_> halfline: precisely
[19:15] <halfline> but there's that kill -TERM -1 or whatever anyway
[19:17] <caolanm> I'm trying out ubuntu lucid beta 1, and upstart doesn't seem to be firing scripts with "start on startup" ...has anyone had success with this?
[19:18] <Keybuk> caolanm: it probably is, but whatever those scripts need isn't ready yet
[19:18] <caolanm> Keybuk: how are those dependencies defined? all the script says is start on startup
[19:19] <caolanm> (I'm working from this guide: http://howtonode.org/deploying-node-upstart-monit)
[19:19] <caolanm> I tried changing it to "start on (local-filesystems and net-device-up IFACE=eth0)"
[19:20] <caolanm> which seems to fire, but I get strange errors regarding missing files
[19:31] <Keybuk> caolanm: you should talk to the maintainers of the software you're trying to update
[19:46] <sadmac> Keybuk: RE: Is this a mountpoint?, why not iterate mtab/proc/wherever and get a list of em?
[19:46] <Keybuk> do you realise how many corner cases that has? :)
[19:47] <sadmac> Keybuk: that + realpath should be == profit
[19:47] <Keybuk> what about if you've got a full filesystem
[19:47] <Keybuk> then you recursively bind mount the /real directory onto /
[19:49] <sadmac> not sure, but that's enough to make me want to not think about it anymore. Your way is fine. :)
[19:49] <sadmac> Keybuk: also did you see my last upstart blogging?
[19:49] <Keybuk> no?
[19:49] <sadmac> Keybuk: http://screwyouenterpriseedition.blogspot.com/2010/04/upstart-service-mangement-modeled-as-bi.html
[19:53] <Keybuk> sadmac: the funny thing is, that blog post makes about as much sense to me as most of your first draft proposals :p
[19:53] <sadmac> Keybuk: I impersonate myself well.
[19:55] <sadmac> Keybuk: also, I would assert that that blog post contains a lifetime supply of release codenames.
[20:37] <notting> sadmac: 577709 updated with brief testing
[21:06] <dvrcoder> question: can i make a upstart script dependent on the start of an oldschool init.d script? say, with "start on SYSVINITNAME"?
[21:14] <sadmac> dvrcoder: you can put an "initctl emit somefunkything" at the end of your sysvinit script, then do start on somefunkything. You could also instrument /etc/rc in a similar way to get such events for everything (which I believe fedora is doing now)
[21:17] <dvrcoder> sadmac: thanks. i'll try and pray it gets my job done :D
[21:38] <sadmac> notting: comitted and tagged. seem to be having some trouble with koji and/or ssl. wanna kick em off?
[21:38] <notting> sadmac: well, i was trolling for comments on the idea
[21:39] <sadmac> notting: among the horrible solutions thats the one that will cause the least screaming.
[21:40] <sadmac> notting: and the good solution might be ready for F-14
[21:40] <sadmac> actually it won't be applicable for F-14
[22:21] <dvrcoder> to create my own upstart script, is it enough to write a blabla.conf and put it in /etc/init, or do i have to register it somewhere additionally?
[23:16] <Keybuk> dvrcoder: ys