Hi, I reorganised my system, and now, /var is a symlink to /temporaire/var Here is the output when I try to stop or restart the NFS server : =============================================== # /etc/init.d/nfs restart * Stopping NFS mountd ... [ ok ] * Stopping NFS daemon ... [ ok ] * Stopping NFS statd ... [ ok ] * Mounting RPC pipefs ... mount: rpc_pipefs is already mounted or /var/lib/nfs/rpc_pipefs is busy mount: according to mtab rpc_pipefs is mounted on /temporaire/var/lib/nfs/rpc_pipefs [ !! ] * Starting NFS statd ... [ ok ] * Exporting NFS directories ... [ ok ] * Starting NFS daemon ... [ ok ] * Starting NFS mountd ... [ ok ] =============================================== So, here is a little fix for the /etc/init.d/nfs init script. $ eix nfs-utils * net-fs/nfs-utils Available versions: 1.0.6-r6 ~1.0.7-r2 Installed: 1.0.6-r6 Homepage: http://nfs.sourceforge.net/ Description: NFS client and server daemons Thanks.
Created attachment 87631 [details, diff] nfs init script and symlinks /etc/init.d/nfs script with symlink /var
We've already told you once to not do such things (Bug 134352) - it's a wrong solution. Use bind -o mount...
And I already told you once that mount -o bind is not possible. If you don't want to support this solution, write it in red in the handbook (with explanations), and in this case, I'll close this bug myself, but please, don't tell me "wrong solution" without arguments. I don't see why /var could'nt be a symlink. So explain me why it's a wrong solution. Is this security related ? Thanks. PS : For now, everything works fine, except this NFS bug.
(In reply to comment #3) > And I already told you once that mount -o bind is not possible. Of course it *is* possible. Please, read the manual, you can have as many bind-mounts to one partition as you need. Also read Bug 112413, Comment #2 for why symlinking is a stupid idea. *** This bug has been marked as a duplicate of 112413 ***
Thanks.
