| tech404 | 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 |
|---|---|---|
| tech404 | s/scripts/events/ | 12:21 |
| Keybuk | tech404: right | 12:21 |
| mlaze | hello there | 19:18 |
| mlaze | any upstart developer around ? | 19:18 |
| sadmac | mlaze: what's up? | 19:21 |
| mlaze | i've been reading upstartcode | 19:22 |
| mlaze | for a while trying to figure out how to use ptrace | 19:22 |
| mlaze | though i'm a little confused | 19:23 |
| sadmac | upstart is not a good ptrace tutorial | 19:23 |
| sadmac | its not even a good use case for ptrace | 19:23 |
| mlaze | i believe so but t's pretty much readable than gdb for example | 19:24 |
| sadmac | there's better options still | 19:24 |
| sadmac | strace for one | 19:24 |
| mlaze | the point is that upstart traces for forks and execs wich is exactly what i'm trying to do | 19:26 |
| sadmac | so does strace :) | 19:28 |
| sadmac | if your use case is similar to ours then ptrace is the wrong way to do it. Its going away soon. | 19:30 |
| sadmac | 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:30 |
| mlaze | yup, after spending some time reading upstart i've figured out that | 19:32 |
| mlaze | waitid and ptrace documentation lacks on some subjects | 19:33 |
| mlaze | sadmac: has i suspected, strace doesn't trace forks using PTRACE_SETOPTIONS | 19:54 |
| mlaze | but thanks for the tips | 19:54 |
| mlaze | anyway | 19:55 |
| sadmac | np | 19:57 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!