Hi,
thank you for your explanation!
But I do not understand why it works with a linux nfs server.
It is possible to disable the file blockeing via nfs on the oi server?
When I create a container, there are some file with the "s" attribute
set in that container and they work flawlessly. What is here the difference?
When I disable the suid-bit on the nfs share, the init.log works out of
box, but it has different file attributes than when it lies on a linux
nfs server.
Regards
Flo
On 06/21/2012 09:01 AM, Philippe Huybrechts wrote:
If you disable init logging , the file will not be created.
in /etc/vz/vz.conf:
INITLOG=no
The underlying issue is that the file is created from outside the container with
the synchronous attribute set. This gets interpreted by the Indiana NFS server
as "mandatory locking": as NFS3 has no locking, all access to the file will be
blocked via NFS, unless the execute bit is set.
So you can either disable init logging or fixup the permissions after creation
of the file (will survive a restart of the container)
It is also something to be aware of when moving vz/private areas from local
storage onto the NFS server, as any file with these bits set will become
inaccessible. Not that there are a lot, but for example Subversion repositories
use it.
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
