Herbert,
You are correct.  Sorry for misquoting you.
Now I'm back to my usual state: Dazed and confused

Here are my vservers
ls -l /vservers/
total 20
drwxr-xr-x  17 root root 4096 Apr  8 11:36 vcrux01
drwxr-xr-x  17 root root 4096 Apr  8 11:36 vcrux02
drwxr-xr-x  17 root root 4096 Apr 22 08:02 vcrux03

Which of the following is correct syntax for the above example? A,B,C,D, or E :)
A) setattr --barrier /vservers
B) setattr --barrier /vservers/
C) setattr --barrier /vservers/vcrux02
D) setattr --barrier /vservers/vcrux02/
E) setattr --barrier /vservers/vcrux02/..
A and B need be run only once
Repeat C,D,E for each vserver

I have been using C.  Is this an issue?  So far things have been running fine.
sig

-----Original Message-----
From: Herbert Poetzl [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 12, 2005 10:45 AM
To: Magnuson, Sig
Cc: [email protected]
Subject: Re: [Vserver] Official copy method?


On Thu, May 12, 2005 at 08:28:36AM -0600, [EMAIL PROTECTED] wrote:
> I was originally doing it that way but Herbert recommended this way.  
> I have not experienced any issues so far.

what I recommended was to use:

        setattr --barrier /vservers/vcrux02/..

instead of

        setattr --barrier /vservers

(spot the dots ;)

and it is because /path/to/.. is not necessarily the 
same as /path 

HTH,
Herbert

> sig
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Bj�rn
> Steinbrink
> Sent: Thursday, May 12, 2005 8:21 AM
> To: [email protected]
> Subject: Re: [Vserver] Official copy method?
> 
> 
> Hello,
> 
> On 2005.05.12 07:48:27 -0600, [EMAIL PROTECTED] wrote:
> >     * Set up vserver barrier
> > 
> > sudo showattr -d /vservers/vcrux02
> > ---bui- /vservers/vcrux02
> > sudo setattr --barrier /vservers/vcrux02
> > sudo showattr -d /vservers/vcrux02
> > ---Bui- /vservers/vcrux02
> 
> the barrier flag is supposed to be set on /vservers (i.e. the directory
> directly above the vserver's root directory). Not sure if setting the
> flag on the vserver's root itself may cause problems with 2.6 kernels.
> 
> HTH
> Bj�rn
> _______________________________________________
> Vserver mailing list
> [email protected]
> http://list.linux-vserver.org/mailman/listinfo/vserver
> _______________________________________________
> Vserver mailing list
> [email protected]
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
[email protected]
http://list.linux-vserver.org/mailman/listinfo/vserver

Reply via email to