[15:16] <scottmmjackson> I'm having a curious issue on Ubuntu 14.04 using upstart to spawn a service that subsequently spawns child processes using `su`. Specifically on Ubuntu 14.04, for some reason, `systemd-logind` is sending SIGHUP to any spawned child. Aside from being confused by seeing `systemd-logind` on the default ubuntu14 box where `init` is `upstart`, I'm also a bit baffled by why systemd-logind is sniping my 
[15:17] <scottmmjackson> service's children with HUP.
[15:18] <scottmmjackson> I've regressed this on Ubuntu 12 and the bug isn't there, which just raises further questions.
[16:06] <xnox> systemd-logind is normal, as we have moved to that from consolekit
[16:08] <xnox> scottmmjackson, why are you using su, instead of using setgid/setuid stanzas? http://upstart.ubuntu.com/cookbook/#setgid
[16:08] <xnox> systemd-logind in this case is just the daemon for session management / reconcilation
[16:24] <scottmmjackson> xnox: su isn't being used in the exec stanza. the parent process is exec'd directly. Its child processes are being forked and calling pam_open_session.
[16:24] <scottmmjackson> The service of which is `su`
[16:24] <scottmmjackson> sorry for the confusion
[16:26] <scottmmjackson> Ironically, however, if the exec line is written like the session-init.conf as listed in this part of the cookbook, forking works just fine: http://upstart.ubuntu.com/cookbook/#non-graphical-sessions-ubuntu-specific
[16:26] <scottmmjackson> Which uses su directly.
[16:28] <scottmmjackson> So there's a fix- wrap it in `/bin/su` like the cookbook says. But I don't feel great not grokking what conditions cause `systemd-logind` to behave this way.