Bug 5772 - dbus-daemon should exit with nonzero status if configured user doesn't exist
Summary: dbus-daemon should exit with nonzero status if configured user doesn't exist
Status: RESOLVED FIXED
Alias: None
Product: dbus
Classification: Unclassified
Component: core (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Havoc Pennington
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 2813
  Show dependency treegraph
 
Reported: 2006-02-01 01:40 UTC by Christian Lohmaier
Modified: 2006-08-25 14:33 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Christian Lohmaier 2006-02-01 01:40:45 UTC
Hi *,

dbus 0.60

When launching dbus-deamon --system without that the user (default:
"messagebus") exists, it will exit immediately with an exit-status of 0, leading
to messages like:

# /etc/rc.d/init.d/messagebus start
Starting system message bus:                                    [  OK  ]

without any instance of dbus-daemon running at all.
The init-script should fail if the deamon cannot be started (no matter for what
reason)

Thank you.
Comment 1 John (J5) Palmieri 2006-02-11 08:18:56 UTC
Ok, so what is happening is we are forking before we drop privlages and the
parent exits fine.  We have a couple of options:

Check if the user exists before we fork.

or

Keep the parent around until we start up and establish a pipe so they can
communicate.

2 sounds better because it will solve any issues where we abort in the child. 
This is not a priority though so it make take some time to get a patch.
Comment 2 John (J5) Palmieri 2006-08-10 14:11:51 UTC
Adding to 1.0 blocker list
Comment 3 Havoc Pennington 2006-08-10 14:16:27 UTC
Another (hacky) approach is to just have the init script sleep for a second or 
two and then check for the pid file...
Comment 4 John (J5) Palmieri 2006-08-25 14:33:35 UTC
This was fixed recently


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.