On 10/12/2011 11:39 PM, Alessandro Ghedini wrote: > Seems like ulatencyd is being signaled to terminate (either SIGABRT, SIGINT, > SIGTERM). That's the only way it could say "abort cleanup" AFAICT. > > Anyway, this is a rather weird bug, and I cannot reproduce it (I'm not even > sure this is actually a bug in ulatencyd itself, or some sort of > incompatibility with other software), therefore I can't be much more > helpful here.
I have some more data points for this, I think.
├─start_kdeinit
├─syndaemon
├─udevd───2*[udevd]
├─udisks-daemon─┬─udisks-daemon
│ └─2*[{udisks-daemon}]
├─ulatencyd─┬─sh
│ └─{ulatencyd}
├─upowerd───{upowerd}
├─vpnc-connect
├─wicd───wicd-monitor
├─wicd-kde───{wicd-kde}
└─wpa_supplicant
This is the pstree output. Do you have any idea what that "sh" shell
process is for. It only is seen during system start-up. If I restart the
ulatencyd daemon, it is not seen. And as far as I can tell, the silently
killed problem is seen only with ulatencyd's system start-up process.
But I could be wrong. I haven't tested it enough of days to conclude.
Any reasons why you do a test first?
# 2 if daemon could not be started
start-stop-daemon --start --quiet --exec $DAEMON --test >
/dev/null \
|| return 1
start-stop-daemon --start --quiet --exec $DAEMON -- \
$DAEMON_ARGS \
|| return 2
I have parallel boot enabled on my sysvinit with CONCURRENCY=makefile.
Given that the shell process is only seen with system start-up i.e.
during real parallel execution of init scripts, I have a feel it is
something wrong there.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: OpenPGP digital signature
