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
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
Am 2012-04-06 14:40, schrieb Chris Ridd:
On 6 Apr 2012, at 11:34, Flo wrote:
Hello,
this is my first time, that I write to a mailing-list!
I have a very big Problem with OpenIndiana 148b NFS-Server.
I need a share for a Linux Client and on the share, there will be openvz
containers. Openvz
On 6 Apr 2012, at 11:34, Flo wrote:
> Hello,
>
> this is my first time, that I write to a mailing-list!
>
> I have a very big Problem with OpenIndiana 148b NFS-Server.
> I need a share for a Linux Client and on the share, there will be openvz
> containers. Openvz is similar to a chroot envirom
Hello,
this is my first time, that I write to a mailing-list!
I have a very big Problem with OpenIndiana 148b NFS-Server.
I need a share for a Linux Client and on the share, there will be openvz
containers. Openvz is similar to a chroot enviroment, so I need that all
permissions are preserved.
