Re: [Vserver] vhashify on Debian / CoW links not breaking on chmod/chown?

2006-02-02 Thread Herbert Poetzl
On Thu, Feb 02, 2006 at 01:02:51PM +0100, Grzegorz Nosek wrote: > 2006/2/1, Herbert Poetzl <[EMAIL PROTECTED]>: > > > - If I modify a file's contents the CoW link is broken properly but > > > after a chmod or chown the link is not broken and I get -EPERM (as the > > > files are marked immutable) -

Re: [Vserver] vhashify on Debian / CoW links not breaking on chmod/chown?

2006-02-02 Thread Grzegorz Nosek
2006/2/1, Herbert Poetzl <[EMAIL PROTECTED]>: > > - If I modify a file's contents the CoW link is broken properly but > > after a chmod or chown the link is not broken and I get -EPERM (as the > > files are marked immutable) - is this expected behaviour? In such a > > situation the links aren't ex

Re: [Vserver] vhashify on Debian / CoW links not breaking on chmod/chown?

2006-02-01 Thread Herbert Poetzl
On Wed, Feb 01, 2006 at 06:29:05PM +0100, Grzegorz Nosek wrote: > Hello all, > > I started playing with vserver unification recently and I'd like to > share my two observations: > > - under Debian (sarge at least) you cannot use the supplied beecrypt2 > packages as they have a slightly different

[Vserver] vhashify on Debian / CoW links not breaking on chmod/chown?

2006-02-01 Thread Grzegorz Nosek
Hello all, I started playing with vserver unification recently and I'd like to share my two observations: - under Debian (sarge at least) you cannot use the supplied beecrypt2 packages as they have a slightly different API (changes are subtle enough that util-vserver will compile but hashcalc wi

Re: [Vserver] Vhashify segmentation fault

2005-11-12 Thread Enrico Scholz
[EMAIL PROTECTED] (alberto) writes: > I finally had time to test vhasify on an i386 with valgrind, attached > is the output. Same debian source package as I used for x86_64 and > same options (added beecrypt2{,-dev} to dependencies so pbuilder > builds it with vhashify). Using 'valgrind' on the '

Re: [Vserver] Vhashify segmentation fault

2005-11-10 Thread alberto
Hi, I finally had time to test vhasify on an i386 with valgrind, attached is the output. Same debian source package as I used for x86_64 and same options (added beecrypt2{,-dev} to dependencies so pbuilder builds it with vhashify). Surprisingly, running it with valgrind doesn't make it segfa

Re: [Vserver] Vhashify segmentation fault

2005-10-31 Thread alberto
Enrico Scholz wrote: ok; please do a 'make check' with 0.30.209 and see if 'hashcalc.sh' succeeds. You can do | ./src/testsuite/hashcalc Makefile.am SHA-1 also, which should output the same hash like 'sha1sum Makefile.am' No luck :( make check gives out (with 0.30.209): PASS: lib/testsuite/

Re: [Vserver] Vhashify segmentation fault

2005-10-30 Thread Enrico Scholz
[EMAIL PROTECTED] (alberto) writes: > Mmmm, so it could be a beecrypt2 problem... right? > I'll try installing from non-debian sources util-vserver and beecrypt > to see what happens. The hash belongs to a real executable though > (according to "file "), not sure which executable but > something t

Re: [Vserver] Vhashify segmentation fault

2005-10-24 Thread alberto
Enrico Scholz wrote: this looks already strange... a hash value with so much '0' is highly improbable... Mmmm, so it could be a beecrypt2 problem... right? I'll try installing from non-debian sources util-vserver and beecrypt to see what happens. The hash belongs to a real executable though (

Re: [Vserver] vhashify

2005-10-24 Thread Thorsten Gunkel
On [Mon, 24.10.2005 09:58], Enrico Scholz wrote: > [EMAIL PROTECTED] (Thorsten Gunkel) writes: > > http://linux-vserver.org/alpha+util-vserver mentions > > that this is possible but I don't understand how to exclude for > > example /var/data1 from vserver foo2. > > 1. /var is excluded by default >

Re: [Vserver] vhashify

2005-10-24 Thread Enrico Scholz
[EMAIL PROTECTED] (Thorsten Gunkel) writes: > In general this works great, but I had once or twice the problem > that a service stopped working because it could not longer write to > its files. Now I like to exclude the affected directory from the > vhashify. http://linux-vserver.org/alpha+util-v

[Vserver] vhashify

2005-10-23 Thread Thorsten Gunkel
Hi *, I also like to ask a vhashify question. I have several vservers and did some time ago the following: # mkdir -p /etc/vservers/.defaults/apps/vunify/hash # mkdir -p /vservers/.hash # ln -s /vservers/.hash /etc/vservers/.defaults/apps/vunify/hash/0 (for all vservers) # mkdir -p /etc/vs

Re: [Vserver] Vhashify segmentation fault

2005-10-23 Thread Enrico Scholz
[EMAIL PROTECTED] (alberto) writes: > I'm running debian sarge on amd64 (though I can reproduce the problem > on another machine running on i386). Custom built debian package for > util-vserver-0.30.208-fix2 with beecrypt2 enabled > ... > lstat("/etc/vservers/.defaults/apps/vunify/hash/0/04/00/000

Re: [Vserver] Vhashify segmentation fault

2005-10-23 Thread Herbert Poetzl
> # vserver webber hashify > Segmentation fault > > # touch exclude (blank excludelist) > > # /usr/lib/util-vserver/vhashify --manually -nv --destination > /etc/vservers/.defaults/apps/vunify/hash/ /vservers/webber/lib/ exclude > Initializing exclude-list for /vservers/webber/li

[Vserver] Vhashify segmentation fault

2005-10-23 Thread alberto
ms running fine. The filesystem (if matters) is xfs. Tried both with SHA-1 and MD5 hashing methods. These are various outputs: # vserver webber hashify Segmentation fault # touch exclude (blank excludelist) # /usr/lib/util-vserver/vhashify --manually -nv --destination /etc/vservers/.defau