[PATCH] dbus-glib patches
David Zeuthen
david at fubar.dk
Mon Mar 17 12:10:05 PDT 2008
On Mon, 2008-03-17 at 19:58 +0100, Rob Taylor wrote:
> I was more concerned about documenting that the bus daemon also has a
> timeout for method calls, defaulting to 25 seconds, so no matter whet
> you set in this function, if your method takes more than 25 seconds an
> error will be returned to the caller.
No, the bus timeout is around six hours or so.
(And if you couldn't do method calls of longer than 25 seconds D-Bus
would be completely useless for non-trivial applications.)
And it's still a complete mystery to me why the bus timeout is there;
FWIW, I consider it a bug that should be fixed along with treating
timeout==INT_MAX as special to avoid silly 49.52 earth day wrap around
issues (because 31 bits is all we use for millisecond timeout).
(Btw, there's another bug in the bus daemon and/or libdbus; it uses wall
clock for accounting purposes meaning that time doesn't stand still
while the system is e.g. suspended or hibernated. On Linux you want to
use the 19th entry of /proc/$pid/stat to avoid this (or similar
constructs). Also, if the clock currently used by the bus daemon isn't
monotonically increasing some people may call this a security bug too.)
David
More information about the dbus
mailing list