[14:38] <wuzle> Hello, I am trying to write a conf file for wicd. It looks like the daemon start, but upstart is tracking the wrong pid. ie if I run 'sudo start wicd', it returns the process as 2806. But soon after, status shows the process as 'stop/waiting' and the pid reported in /var/run/wicd/wicd.pid is 2807. Is upstart tracking the wrong process here? Is there a way to fix it?
[15:07] <sadmac> wuzle: could be a weird one. strace it and see how many times it forks
[15:09] <wuzle> sadmac: I tried just starting wicd in the foreground from upstart. It seams to work, but is this a bad thing?
[15:10] <sadmac> wuzle: you mean you told it not to daemonize?
[15:10] <sadmac> wuzle: that's a fantastic thing. Always the preferred option
[15:10] <sadmac> well, you don't get the "readiness" indicator that forking provides, but usually its a fine thing.
[15:11] <wuzle> sadmac: yes, there was a command line option to wicd.
[15:11] <wuzle> sadmac: I mean, yes, I told it not to deamonize
[15:11] <sadmac> wuzle: yeah, that's fine
[15:12] <ion> As soon as Upstart 0.10 is released, letting it fork is a good thing. Until that, it’s often best to let it stay in foreground.
[15:13] <wuzle> BTW, this all started because the wicd init.d script wasn't working on startup (Ubuntu 9.10). But worked fine if I call '/etc/init.d/wicd start'. The guys on the wicd chat room thought it was because dbus wasn't started yet. And I noticed dbus moved to upstart. So that is why I have come down this road.
[15:17] <jfanj> I am having a problem with many of my daemons not starting on boot and was wondering if anyone here could help me out?