On Wed, Jan 28, 2015 at 02:38:52AM +0100, Lennart Poettering wrote: > To clarify this: if people do this, then this pulls in > systemd-udev-settle.service, which slows down boot. Every service that > does that is hence a majour source of slowness.
> It's a hack to use this, not a solution. Well, yes. There aren't really any good solutions with our event driven model - we never "finish" booting, we just get to a point where nothing has been happening for a while. I have been thinking that we need to just admit that properly and do something timer based - have a timer that gets reset every time we instantiate something, then do all our "end of boot" actions when nothing happened for a while. It's not elegant but I don't think elegant is a realistic goal here.
signature.asc
Description: Digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
