Subject: Re: [vserver] chroot barrier problem when consolidating var and etc
From: randall <randall@songshu.org>
Date: Thu, 02 Oct 2008 15:49:43 +0200

Herbert Poetzl wrote:
>
>>
>> node1:/VSERVERS# showattr /VSERVERS/
>> ----Bui- /VSERVERS/
>>     
>
> if ns1, web, web2 and hosting are the root
> directories of Linux-VServer guests, then the
> barrier above is correct
>   
they were.
>   
>> ----bui- /VSERVERS/ns1
>> ----bui- /VSERVERS/web
>> ----bui- /VSERVERS/hosting
>> ----bui- /VSERVERS/web2
>> node1:/VSERVERS# showattr /VSERVERS/web2/
>> ----bui- /VSERVERS/web2/
>> ----bui- /VSERVERS/web2/etc
>> ----bui- /VSERVERS/web2/barrier
>> node1:/VSERVERS# showattr /VSERVERS/web2/etc/
>> ----bui- /VSERVERS/web2/etc/
>> ----bui- /VSERVERS/web2/etc/web2
>> node1:/VSERVERS# showattr /VSERVERS/web2/
>> ----bui- /VSERVERS/web2/
>> ----bui- /VSERVERS/web2/etc
>> ----bui- /VSERVERS/web2/barrier
>> node1:/VSERVERS# showattr /VSERVERS/web2/barrier
>> ----bui- /VSERVERS/web2/barrier
>> ----Bui- /VSERVERS/web2/barrier/var
>>     
>      ~~~~
>  that one really looks wrong to me, unless you
> actually did put a guest in /VSERVERS/web2/barrier/var
>   
i did put a guest there, and it was the one not working.
> the rule for the barrier is quite simple, although
> people tend to unnecessarily complicate it:
>   
i did not even know about it ;)
> you want a barrier on /path/to/guest/.. for each
> guest (which usually only affects a single directory,
> as all guests are located in the same place, but
> might as well affect one directory per guest)
>
> HTH,
> Herbert
>   
in this case the /VSERVER barrier was blocking /VSERVERS/web2/barrier/var,

so i can confirm it simply worked after removing the other guests and 
removing ----Bui- /VSERVERS/