=== tck [n=tck@212.2.170.189] has joined #upstart === bicchi [n=albert@adsl-065-006-167-199.sip.mia.bellsouth.net] has joined #upstart [04:13] since upstart replaced /etc/inittab. how can i set the runlevel at startup? === mbiebl [n=michael@e180069185.adsl.alicedsl.de] has joined #upstart === Md [i=md@freenode/staff/md] has joined #upstart === sadleder [n=sadleder@p50814541.dip0.t-ipconnect.de] has joined #upstart === Keybuk [n=scott@quest.netsplit.com] has joined #upstart === Md [i=md@freenode/staff/md] has joined #upstart === juergbi [n=juerg@80-219-19-183.dclient.hispeed.ch] has joined #upstart === tck [n=tck@A-72-212.cust.iol.ie] has joined #upstart === tck [n=tck@A-72-212.cust.iol.ie] has joined #upstart === bicchi [n=albert@adsl-065-006-167-199.sip.mia.bellsouth.net] has left #upstart [] === phoenix24 [i=xqjjd@ns37986.ovh.net] has joined #upstart === sadleder [n=sadleder@p50814541.dip0.t-ipconnect.de] has left #upstart [] [06:16] Stupid question alert: What is the canonical way to manage a daemon that insists on detaching itself from the console? [06:17] there isn't one just yet [06:17] officially you place "daemon" in the job definition [06:17] that will cause upstart to not automatically leave the spawned state [06:17] Ah. [06:17] waiting for some as-yet-unimplemented something to obtain the pid of the process to supervise [06:17] It might interest you to know that apache2 is one such daemon. [06:18] indeed === tck [n=tck@A-78-162.cust.iol.ie] has joined #upstart === Md_ [i=md@freenode/staff/md] has joined #upstart === Md_ is now known as Md === mbiebl [n=michael@e180070076.adsl.alicedsl.de] has joined #upstart