[12:21] So is the reason that almost all the scripts simply trigger old scripts due to the fact everything has not been finalized? I thought we would have seen more services with their own events by now. [12:21] s/scripts/events/ [12:21] tech404: right [19:18] hello there [19:18] any upstart developer around ? [19:21] mlaze: what's up? [19:22] i've been reading upstartcode [19:22] for a while trying to figure out how to use ptrace [19:23] though i'm a little confused [19:23] upstart is not a good ptrace tutorial [19:23] its not even a good use case for ptrace [19:24] i believe so but t's pretty much readable than gdb for example [19:24] there's better options still [19:24] strace for one [19:26] the point is that upstart traces for forks and execs wich is exactly what i'm trying to do [19:28] so does strace :) [19:30] if your use case is similar to ours then ptrace is the wrong way to do it. Its going away soon. [19:30] Granted only Keybuk knows the /right/ way, and he's not giving out the details (you can dig them out of obscurity in the kernel source if you want to). [19:32] yup, after spending some time reading upstart i've figured out that [19:33] waitid and ptrace documentation lacks on some subjects [19:54] sadmac: has i suspected, strace doesn't trace forks using PTRACE_SETOPTIONS [19:54] but thanks for the tips [19:55] anyway [19:57] np