[11:10] <dariocravero> hi all, I have an upstart script that needs some of the user's secondary groups being set and after a while without knowing what was going on I realised that setgid only sets one group for the user. I've found this SO post (http://superuser.com/a/225355/134737) that highlights a few alternatives to it, it's a bit old though, are those still relevant or is there any better way to go about it?
[11:12] <dariocravero> should I use start-stop-daemon instead?
[11:12] <dariocravero> do I still need to use setuid and/or setgid in that case?
[11:13] <dariocravero> thanks :)
[12:23] <Phlogistique> hi
[12:23] <Phlogistique> I'm trying to run an upstart-based system (Ubuntu) under systemd-nspawn
[12:24] <Phlogistique> Did anyone do that successfully?
[12:25] <Phlogistique> http://sprunge.us/LTGD so far I get this in the console. does this "Handling starting/failed event" message mean that mountall has failed?
[12:25] <Phlogistique> I believe I would have to de-activate mountall but still emit the events that it would emit on success
[19:11] <nikkie> Hi folks.  I'm having some issues with a pair of upstart scripts.  I'm running several instances of the same job, so I have a start-this-once script and a many-many-instances script.  The jobs stop correctly and start, but when I run start, it hangs on the invocation instead of telling me the job started.  Upstart doesn't have the pid of the N jobs it starts.  Here are my scripts:
[19:11] <nikkie> https://gist.github.com/nikolawannabe/4f5bcdd1a6954038f23f
[19:26] <nikkie> I removed task and it no longer hangs. Not sure if that is the correct fix.  Any commentary would be appreciated!