[02:27] I'm thinking out loud here, but would it make sense to support something like taskset(1) or sched_setaffinity(2) for that matter, in upstart? [09:40] looks like upstart follows fork or spawned children of a process it's monitoring, any way to turn that behaviour of? it leads to a lot of overhead coming from the init process [09:45] out of interest, have you measured that overhead and found it to be too high for your environment? [09:49] it is the #1 process measured in cputime :) [09:51] Upstart only uses ptrace for "expect fork" and "expect daemon". The overhead of using ptrace is negligible for starting such jobs. [09:54] ah ok, well I made a nagios init. what happens is that everytime nagios spawns a process, somehow init gets triggered [09:55] this is what init does in a strace: http://pastebin.com/JSkKFE7p [09:58] upstart reaps zombie processes (as do all init systems). That is correct behaviour and not something you can (or would want to) turn off. [09:59] ok thanks, I'll look for another way then [09:59] I'm confused. Is there a problem with upstart on your system? [10:00] actually no, I think I just understand what you mean. doesn't matter how I start these 1000's of processes. init still has to check them [10:00] so this isn't really an issue, probally more of a misunderstanding on my part :) [10:01] yes. If init didn't do this, your process table would eventually fill up with zombies, which might eventually kill the system. [10:09] yeah, makes sense. thanks for explaining [10:09] no problem