http://bugzilla.suse.com/show_bug.cgi?id=1006815 http://bugzilla.suse.com/show_bug.cgi?id=1006815#c24 José Iván López González <jlopez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jlopez@suse.com Resolution|--- |FIXED --- Comment #24 from José Iván López González <jlopez@suse.com> --- (In reply to Neil Brown from comment #7)
No, it doesn't really make sense for the nfs-client service to mount filesystems. systemd should do that directly. Whenever yast adds something to /etc/fstab it should "systemctl daemon-reload" so that the generators get run and systemd learns about the new contents of /etc/fstab. Do you see any problem with making yast do that?
Using "systemctl daemon-reload" was tricky under certain scenarios (e.g., for a NFS share directly mounted by the user but not included in the fstab). Finally we have decided to delegate the mounting/unmounting actions to the yast storage stack. Thanks to that, now on the behavior is exactly the same when the nfs client is used standalone and when it is used through the Expert Partitioner. Fixed by yast2-storage-ng 4.2.73 and yast2-nfs-client 4.2.5. -- You are receiving this mail because: You are on the CC list for the bug.