[29.05.2014 17:31] [Andrey Borzenkov]:
В Wed, 28 May 2014 21:02:12 -0400 Cristian Rodríguez <crrodriguez@opensuse.org> пишет:
El 28/05/14 20:25, Ruediger Meier escribió:
So it's not possible to umount(2) /srv forever? "systemctl start apache" would mount it again or what? Even if I have mounted something else there in the meanwhile? That's insane. Don't add such stupid deps per default.
That's not how things work, if you manually umount the filesystem it should stay that way.
Actually that's how things work. If you put "Requires=srv.mount" in apache.service, starting apache.service will attempt to mount /srv.
Which works as designed and documented.
Of course it does not mean design cannot be improved ... :)
In this case I wonder how one will catch all cases... Maybe /srv is on the root filesystem, but /srv/www is mounted separately, /srv/ftp also, and /srv/git and other subdirs too. How can this be configured? Or /srv is on the root fs, and only /srv/ftp and /srv/www are mounted separately, other subdirs like /srv/tftpboot are kept on the root fs. I think it is hard to guess for any tool - first the server configuration must be read to find out where the software expects its data, then fstab must be searched for entries from the expected dir upwards. And all this at installation time, what means that you can change the config afterwards, and if the respective admin is not aware of those entries for systemd, you may get a "mounting knot" in the system ;-) Just imagining... :-D Werner -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org