Description of problem:
I bumped into that sort of by an accident. Immediately after
service messagebus restart
a check 'service haldaemon status' shows "is running..." but
if this is repeated after a short delay, say ten seconds, then
it comes as "is stopped". No log traces or anything else. Just
hald goes away.
One can say "don't do it, then" but a restart of a messagebus
service may happen for some reasons. Is an effect on hald intended?
It could be possible in /etc/init.d/messagebus to check in 'restart'
if hald is running and restart it too if this was the case. It looks
that this would prevent such surprises.
Version-Release number of selected component (if applicable):
There's a good reason the messagebus isn't restarted on package upgrades.
Nevertheless hald does try to connect to the bus when it disappaers and jumps on
it if it becomes available. If this doesn't work it's a bug.
This was fixed by this commit
and that code is in RAWHIDE.