[12:10] hi [17:00] hi [17:00] im using upstart in karmic [17:02] is there any reason why an event script is not showed with initctl list, but if i change its name it is listed? [17:56] foolano: so if you have a script with a particular name it won't show up? [17:56] sadmac2: it was really weird. I had this script and it didnt show up, i just copied with another name and it showed up [17:57] sadmac2: kill -HUP 1 fixed it though [17:57] but it was really strange [17:57] foolano: inotify glitch? [17:57] prolly [17:57] i was like wtf is wrong with that name :) [17:58] heh [17:58] sadmac2: anyway, im gonna repeat the same tests a few times cuz im testing new packages, so if it happens again, I'll let you guys know [17:59] i can even recordmydesktop to prove it :P [17:59] foolano: sweet [18:00] i was wondering if i should include the "kill -HUP 1" after copying the scripts [18:00] or it should *always* work without that? [19:41] just started reading about upstart. [19:41] does it have another command for update-rc.d? [19:46] swathanthran: not heard of that command [19:46] foolano: it should always work without HUP [19:47] thats the usual command to update sys-v init script.. like update-rc.d -f gdm remove disables gdm.. [19:47] sadmac2: ^ [19:47] upstart doesn't have an intersection to that area? [19:49] like, as i read upstart as a replacement to usual init scripts, i was checking about ways to configure that.. [19:50] ah i just see ubuntu having update-rc.d itself for updating init scripts.. and at the same time having upstart for init! [19:50] where am i wrong? [19:50] swathanthran: for the upstart jobs themselves there's no equivalent really right now. If upstart is acting as a layer over sysv, the sysv jobs should be manipulable by all the old mechanisms [19:50] swathanthran: yes, upstart has a set of jobs that basically act like sysv so you can use old-style sysv scripts. [19:51] oh thats cool..so its really an intersection;-) [19:51] ah what ever..;-) anyway thats cool..