How do y'all test?
oliv__a at users.sourceforge.net
Tue May 18 03:10:02 PDT 2004
Tako Schotanus [Tue, 18 May 2004]:
> I attached the trace but what I was wondering is where dbus writes
> its errors to, because it's obvious that in one of the last lines
> of the trace "write(2, "Failed to start message bus: Cou"..., 81) =
> 81" it tries to tell what has gone wrong, but I haven't been able
> to find a log file or anything like that. Or do I need to
> re-compile with "verbose mode" for this to work?
> hmmm... wait...
> Well at least with strace -f -s 100 I now know what the error is, but I
> would still like to know where this output goes to ;-)
> BTW: the error was "write(2, "Failed to start message bus: Could not get
> UID and GID for username \"messagebus\"\n", 81) = 81", so you were right
You can't see anything because dbus-daemon-1 redirects all standard
descriptors to /dev/null.
To prevent this, you need to comment out the <fork/> line in the
config file or use the DBUS_DEBUG_OUTPUT environment variable to keep
More information about the dbus