On 17/11/14 23:12, Simon McVittie wrote: > I happened to notice (via LWN) that Mageia have reverted part of a > recent dbus denial-of-service fix.
Now discussed upstream at <https://bugs.freedesktop.org/show_bug.cgi?id=86431> > I'll look into adding logging when this timeout is hit. Paul, would you mind trying a patched dbus which can confirm whether you're hitting this timeout or something else? Source and i386 binaries here, with hashes signed by my key in the Debian keyring: <https://www.pseudorandom.co.uk/~smcv/20141118dbus/> or if you're comfortable rebuilding Debian packages, you can rebuild dbus with the logging patch from <https://bugs.freedesktop.org/show_bug.cgi?id=86431#c4>, like this: <https://www.pseudorandom.co.uk/~smcv/20141118dbus/dbus_1.8.10-1+auth1.diff>. With that installed, please configure dbus for the potentially problematic 5-second timeout: if you have already configured a custom <limit name="auth_timeout">, please remove it. Then reboot enough times to see the bad behaviour, and collect the syslog or journalctl. You can set an arbitrary timeout in milliseconds by putting something like this in /etc/dbus-1/system-local.conf: <busconfig> <limit name="auth_timeout">30000</limit> </busconfig> The old default was 30000, and if this is indeed what's causing your startup problems, I'm proposing to return to that. On the oldest machine I had conveniently to hand, running testing with systemd and the GNOME desktop task, I could go as low as 100 (0.1 second) and get to the gdm prompt without seeing any problems. 5 (0.005 seconds) caused ModemManager to fail, and 1 (0.001 seconds) caused lots of services to fail, including systemd-logind. S -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
