[01:20] <nirvdrum> Hi.  I'm trying to start up a job using setuid, but I need that to work as if it were a login shell.  I.e., I need the unprivileged user's environment setup through the files in /etc/profile.d/  Is that doable?
[02:25] <mattbillenstein> hi all
[02:25] <mattbillenstein> how do I clear the state for a stuck job?
[02:26] <mattbillenstein> status says my job is start/killed with a pid
[02:26] <mattbillenstein> but that pid doesn't exist
[02:26] <mattbillenstein> so stop just hangs
[02:26] <mattbillenstein> and start thinks it's already running
[02:28] <mattbillenstein> like, does upstart store this state somewhere?
[02:47] <mattbillenstein> anyone around?
[12:56] <etank> i am having an issue with the order that daemons are starting in 12.04 i think
[12:56] <etank> we use nis + autofs and i think that ypbind is trying to start before network-manager is up
[12:57] <etank> ypbind shows that it is running after a boot but ypwhich says "Can't communicate with ypbind"
[12:57] <etank> autofs is also running and it shows a pid
[12:58] <etank> ypbind however does not list a pid
[12:59] <etank> the only thing i can do to get the system working after a boot is to issue a "service ypbind restart; service autofs restart"
[13:00] <etank> is there a more upstart'ish way of doing this so i dont have to do it manually or add a sleep to rc.local?
[13:53] <JanC> etank: are ypbind & autofs upstart jobs or sysvinit scripts?
[13:56] <JanC> seems like they are sysvinit scripts?
[13:57] <etank> they are upstart jobs it seems
[13:57] <etank> they link to /lib/init/upstart-job
[13:57] <etank> they being start-ypbind, ypbind, network-manager  and autofs
[13:58] <JanC> if there is an /etc/init/autofs etc. then they are upstart jobs indeed
[13:58] <etank> there are
[13:58] <etank> it seems that ypbind is starting too soon
[13:59] <etank> network seems to not be up when ypbind is trying to start
[13:59] <etank> should be network-manager -> ypbind -> autofs
[14:00] <JanC> network-manager being started doesn't mean network is up
[14:00] <JanC> there are events when network comes up though
[14:02] <JanC> net-device-up
[14:03] <etank> ok
[14:03] <etank> upstart is all new to me
[14:03] <JanC> so I guess those upstart jobs should wait for those events
[14:04] <etank> net-device-up needs to happen for non loop back interfaces
[14:04] <etank> then ypbind can start since it can contact the ypservers
[14:04] <etank> then autofs can start since nsswitch says to talk to nis for automounts
[14:05] <etank> you could substitute ldap in for ypbind for systems that authenticate to ldap i guess but the idea would be the same
[14:06] <JanC> etank: maybe there are more people in #ubuntu-server who are familiar with this particular type of setup
[14:07] <etank> network-manager.conf does not have a emit statement for net-device-up
[14:07] <etank> i will ask in ubuntu-server as welll
[14:08] <JanC> the "emit" stanza is just documentation anyway
[14:13] <JanC> and I think the actual events might be emitted by another job or maybe upstart-udev-bridge -- see upstart-events(7) 
[21:24] <Telenull> Hello everyone. Is there a way to exec as an unprivileged user from an upstart? I've tried a few things that show up on superuser (using su -s and sudo -u, but they all cause it to start as root still). any ideas?
[22:04] <SpamapS> Telenull: two ways actually :)
[22:04] <Telenull> :P I ended up getting it working with sudo.
[22:04] <SpamapS> Telenull: if you have upstart 1.5 (Ubuntu 12.04 basically) then you can use 'setuid' and 'setgid' as keywords
[22:05] <Telenull> oh neat.
[22:05] <SpamapS> Telenull: otherwise sudo or start-stop-daemon work
[22:05] <Telenull> unfortunately i'm still on 10.04.
[22:05] <Telenull> the update to 12.04 will happen for me in about three months.
[22:05] <SpamapS> Telenull: there are some ideas in http://upstart.ubuntu.com/cookbook/
[22:05] <Telenull> Thanks for the info though!
[22:05] <Telenull> Awesome, thanks.
[23:57] <wookienz> morning any knowledgeable folk around?