Hello Michael,
Thanks for looking at this.
On 22/10/16 11:07, Michael Biebl wrote:
Am 27.07.2016 um 02:59 schrieb John Pearson:
Hello Michael,
After the problem first occurred I reviewed bug #767468 and purged both
cgmanager and sytemd-shim, but the problem remained. And, of course,
/proc shows systemd-machined (and only systemd-machined) still "thought"
/nfs/home was mounted.
Why is systemd-machined running? Do you have any systemd-nspawn
containers running where /home is symlinked or bind-mounted?
I have no idea - it was installed as part of the systemd package, and
starts automatically at boot. The machine runs a single KVM instance
hosting Windows 7, managed by libvirtd.
If you stop systemd-machined, is the problem gone?
That seems to fix it without any obvious drawbacks, but I assume I'd
have to do the same after each reboot.
Regards,
John Pearson.
--
*email:* j...@huiac.com
"The greatest shortcoming of the human race
is our inability to understand
the exponential function."
- Albert Allen Bartlett
*web:* http://www.huiac.com/
*mob:* +61 407 391 169
*phone:* +61 8 7127 6275
