On 07/11/2017 06:15 AM, Tom Horsley wrote:
On Tue, 11 Jul 2017 13:01:48 +0200
Robert Moskowitz wrote:
The only option, so far, has been to force the image off, then restart
it, then get everything working again.
There appear to be a near limitless number of things which systemd
doesn't properly wait for at boot time. This may be another.
If you really want a virtual machine always running, I'd change
the setting to say don't restart at boot, then add something like
this to rc.local:
It appears you misunderstood the question and turned it into another
attack on systemd which is unlikely to be involved here at all. And if
you think "systemd" isn't waiting for the right things, then file a bug
and get the config files fixed. It's not a problem with systemd itself.
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
