Ticket #104 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

/etc/init.d/netmount does not start in openvz due to noopenvz keyword

Reported by: Alexander <piavka@cs.bgu.ac.il> Owned by: roy
Priority: major Milestone:
Component: init.d scripts Version:
Keywords: Cc:


Hi, I've some openvz containers which need to mount nfs shares
but in recent openrc-0.2.5 /etc/init.d/netmount has noopenvz keyword.

I don't know the reasoning behind not allowing nfs mount from openvz container
but certainly it's legitimate to have nfs mounts, and in my case its a must have
on several containers. (I know i can have nfs mounts in the Hardware node itself and make bind mounts from openvz containers, and this it how i initialy worked
but i found this setup to be too problematic).

Here is the trivial patch

--- init.d/netmount.in.orig 2008-08-12 15:08:47.000000000 +0300
+++ init.d/netmount.in 2008-08-12 15:09:04.000000000 +0300
@@ -35,7 +35,7 @@

need net ${pmap}
use afc-client amd autofs openvpn
use dns nfs nfsmount portmap rpcbind rpc.statd

  • keyword nojail noopenvz noprefix novserver

+ keyword nojail noprefix novserver




Change History

comment:455 Changed 2 years ago by Alexander <piavka@cs.bgu.ac.il>


comment:457 Changed 2 years ago by roy

  • Status changed from new to resolved
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.