On Thu, 26.05.16 11:29, Felix Miata ([email protected]) wrote: > Did this ever get fixed? IOW, sometimes a service will fail to start when a > system is started, or later, after a session of updating, a previously > operating service fails to restart, or a newly installed service fails to > start, or a service is removed. Then at shutdown/reboot time, systemd pauses > 90 seconds with a message about trying to *start* a service. I think I most > often notice this when I try to hold down CAD after a normal shutdown/reboot > order gets stuck or seemingly ignored. At such times I typically see an > "endless" string of failing to save sound card state messages.
I have never heard of something like this. And what you describe is not really how systemd works. At shutdown, we actually only shut down services, we don't start any. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
