Re: [Vserver] Create a guest
On Wednesday 29 March 2006 16:14, Albert Shih wrote: > Hi all > > Maybe very stupid question, but have a server running FC4 with > vserver-patch kernel. > > I want launch two guest with same version of linux but I don't want make a > big copy. How can I do that ? > I'm using unionfs (http://www.am-utils.org/project-unionfs.html) to have a vserver running on a union mount. Basically it works as follows: I have 3 dirs: xxx/root (original tree, must not be modified by the vserver) xxx/vserver/mnt (that's where the vserver runs - it's root dir) xxx/vserver/changes (thats where the unionfs changes go) now I do a union-mount to have xxx/root mounted RO on xxx/vserver/mnt, and xxx/vserver/changes mounted RW so the vserver can write to it's / If the vserver goes berserk and deletes it's files or something, I just unmount the union, delete the changes and start again with a fresh one. I didn't try this contruct with the host root (/), though, but I think it should work somehow after some modification on the union mount (remove some init scripts for the vserver that require hardware access etc.) You have to slightly modify the unionfs sources to work together with the vserver patch. Andreas ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Debian packages (Was: Re: [Vserver] vserver 2.0.2 patch for kernel 2.6.15.6)
New Debian package (but for 2.6.16) ... http://packages.debian.org/unstable/base/linux-image-vserver-amd64-k8 http://packages.debian.org/unstable/base/linux-image-2.6-vserver-amd64-k8 http://packages.debian.org/unstable/base/linux-image-2.6.16-1-vserver-amd64-k8 Linux kernel 2.6.16 image on AMD64 K8 machines This package provides the binary image and pre-built loadable modules for Linux kernel 2.6.16 on 64bit AMD Athlon64, AthlonFX, Opteron and Turion64 machines. This packages is produced using an updated kernel packaging system and replaces older kernel-image packages -- 5o Peter.Mann at tuke.sk ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Re: Vhashify segmentation fault
> There was some mail exchanges some month ago on the list between > Enrico and Alberto about vhashify SIGSEGV on Debian x86_64. How did > this end ? I seem to have the same problem: Does 'make check' report errors for the hashcalc* tests? If so, somebody with an x86_64 and Debian- and beecrypt knowledge should take a look at src/testsuite/hashcalc-plain.c and see what is going wrong there. It does : SHA-1 mismatch at rand-0 FAIL: src/testsuite/hashcalc-plain.sh SHA-1 mismatch at rand-0 FAIL: src/testsuite/hashcalc.sh It turns out that compiling and using the last beecrypt version (4.1.2) instead of using a debian package makes the problem disappear. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] vserver 2.0.2 patch for kernel 2.6.15.6
Gerald Hochegger wrote: ok - I'll try to package an ubuntu kernel with the vserver devel patch also. But I'm not able to upgrade the Ubuntu kernel with all Ubuntu patches to 2.6.16 - I've to stick with the Ubuntu provided 2.6.15.6 kernel. This leads back to the starting point of the thread. I need vserver patches for vanilla kernel 2.6.15.6 And as Björn Steinbrink pointed out at the beginning of the thread, you can quite easily extract the changes using interdiff, which is what I normally do for the Fedora kernels (when I haven't applied the deltas already). -- Daniel Hokka Zakrisson GPG id: 06723412 GPG fingerprint: A455 4DF3 990A 431F FECA 7947 6136 DDA2 0672 3412 ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Re: Vhashify segmentation fault
> There was some mail exchanges some month ago on the list between > Enrico and Alberto about vhashify SIGSEGV on Debian x86_64. How did > this end ? I seem to have the same problem: Does 'make check' report errors for the hashcalc* tests? If so, somebody with an x86_64 and Debian- and beecrypt knowledge should take a look at src/testsuite/hashcalc-plain.c and see what is going wrong there. It does : SHA-1 mismatch at rand-0 FAIL: src/testsuite/hashcalc-plain.sh SHA-1 mismatch at rand-0 FAIL: src/testsuite/hashcalc.sh ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Qmail inside vserver 2.0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi
Timothy Arnold wrote:
> Just wondered if anyone has had any issues starting Qmail inside a vserver
> (2.0). I have a straight thing where Qmail will not start on "boot". The
> init script does run, but the daemons appear to crash. Once the vserver
> has started, I can login and run /etc/init.d/qmail start and it works.
>
> Some people have suggested that I change init, as I am using the standard
> Qmail start/stop script but I think that this might be more fundamental ?
i had trouble getting djbdns to work until a friend helped out. these are some
notes he wrote up - the problem was not with the djbdns but with the daemontools
supervisory processes, which i suspect may be similar for qmail (i have never
used qmail, so don't know exactly how it works):
getting daemontools to launch
Installing the daemontools packages adds the following line to /etc/inittab:
SV:123456:respawn:/command/svscanboot
and then instructs the init process to rescan its file, which kicks off
svscanboot. svscanboot is the grandaddy process for all the daemons handled by
daemontools. it is responsible for kicking off svscan, which watches the
contents of /service, and launches a supervise process for each well-formed
configuration directory linked there.
on a vserver, there is no true init process running. the only init process is
the one which runs on the host. so modifying /etc/inittab in the vserver and
attempting to instruct init to rescan it did nothing.
however, when a vserver starts up, it does kick off the appropriate sysvinit
scripts for its desired runlevel. So i (dkg) wrote a simple
/etc/init.d/daemontools script to start and stop svscanboot. i based the script
off of /etc/init.d/skeleton.
that script looks something like:
#! /bin/sh
#
# daemontools for launching /etc/svscanboot from sysvinit instead of
/sbin/init.
#
# author: dkg
set -e
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DESC="daemontools"
NAME=svscanboot
DAEMON=/command/svscanboot
PIDFILE=/var/run/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME
# Gracefully exit if the package has been removed.
test -x $DAEMON || exit 0
#
# Function that starts the daemon/service.
#
d_start() {
start-stop-daemon --start --background --make-pidfile --quiet --pidfile
$PIDFILE \
--exec $DAEMON
}
#
# Function that stops the daemon/service.
#
d_stop() {
start-stop-daemon --stop --quiet --pidfile $PIDFILE \
--name $NAME
echo "not cleaning up svscan and readproctitle subprocesses
appropriately. dkg is lazy."
}
#
# Function that sends a SIGHUP to the daemon/service.
#
d_reload() {
start-stop-daemon --stop --quiet --pidfile $PIDFILE \
--name $NAME --signal 1
}
case "$1" in
start)
echo -n "Starting $DESC: $NAME"
d_start
echo "."
;;
stop)
echo -n "Stopping $DESC: $NAME"
d_stop
echo "."
;;
restart|force-reload)
#
# If the "reload" option is implemented, move the "force-reload"
# option to the "reload" entry above. If not, "force-reload" is
# just the same as "restart".
#
echo -n "Restarting $DESC: $NAME"
d_stop
sleep 1
d_start
echo "."
;;
*)
# echo "Usage: $SCRIPTNAME {start|stop|restart|reload|force-reload}" >&2
echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload}" >&2
exit 1
;;
esac
exit 0
This might well be the wrong way to go about it, but i'm not sure.
www.nongnu.org/util-vserver/doc/conf/configuration.html has some (unclear to me)
instructions about how to deal with the non-standard init situation under a
vserver. However, since the standard initscripts from the sysvinit runlevels
seemed to be working, and svscanboot (cr.yp.to/daemontools/svscanboot.html)
should never really need to restart, the simplest thing for me to do was to add
the initscript.
- --
love and solidarity,
--gdm
http://docs.indymedia.org/view/Main/GarconDuMonde
gpg id: 0x594B97C2
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Darwin)
iD8DBQFELFUCDiVJRFlLl8IRAnKwAKCEYeI3mhHJ01pIb5akFNPDnPX1KwCeN0aQ
hFt55fYt8CFCGyWPmwlb9aw=
=5i4Y
-END PGP SIGNATURE-
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] vserver 2.0.2 patch for kernel 2.6.15.6
On Thu, Mar 30, 2006 at 02:51:59AM +0200, Herbert Poetzl wrote: > On Thu, Mar 30, 2006 at 12:08:29AM +0200, Gerald Hochegger wrote: > > On Wed, Mar 29, 2006 at 03:55:10PM +0200, Herbert Poetzl wrote: > > > On Wed, Mar 29, 2006 at 12:15:05AM +0200, Gerald Hochegger wrote: > > > > On Tue, Mar 28, 2006 at 11:30:50AM +0200, Herbert Poetzl wrote: > > > > > sure I _could_ support a dapper vserver kernel, but, > > > > > and here is the important fact, this would not scale ... > > > > > > > > > > in the very near future, I'd be supporting 20 different > > > > > kernels from at least 10 different distros, and there > > > > > would be no time left for development, so some other > > > > > model is required to solve this, and it's actually > > > > > quite simple ... > > > > > > > > > > a) somebody steps up as 'new' maintainer for a dapper > > > > > vserver kernel (preferable stable and devel) > > > > > > > > > I'm willing to help, but i'm a little anxious with the > > > > stepping forward as my free time is very limited. > > > > > > > > > b) that somebody commits himself/herself to tracking > > > > > changes in dapper _and_ vserver in the forseeable > > > > > future > > > > > > > > > I'm using a script to automate this task, so tracking > > > > a stable Ubuntu release and a stable Vserver release > > > > should be quite straightforward. > > > > (script and patches are available at > > > > https://wiki.ubuntu.com/VServer) > > > > > > > > > c) that person contacts me and we arrange to do an > > > > > initial port on that kernel, something which can > > > > > be considered a _known_good_ state > > > > > > > > > For Ubuntu the Dapper 2.6.15.6 kernel and 2.0.2 Vserver > > > > patch (slightly modified for dapper) would be a good start. > > > > > > is there any reason for not supporting the devel branch? > > > (not that I have a problem with that, just curious) > > > > > I'll try to build vserver devel kernel packages after Dapper is > > released and the Dapper+1 kernel (2.6.17rc..) appears. > > > > Till summer I don't have the time to track two branches. > > i.c. so the 'motto' for ubuntu folks will be: > if you want features, build a vanilla kernel > works for me! > ok - I'll try to package an ubuntu kernel with the vserver devel patch also. But I'm not able to upgrade the Ubuntu kernel with all Ubuntu patches to 2.6.16 - I've to stick with the Ubuntu provided 2.6.15.6 kernel. This leads back to the starting point of the thread. I need vserver patches for vanilla kernel 2.6.15.6 I'll then provide the diffs to get the vanilla vserver patch to compile and hopefully work on Ubuntu and create an Ubuntu archive for easy installation/testing of the resulting debs. Gerald ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Qmail inside vserver 2.0
Hi, Been running qmail-send, qmail-pop3d and qmail-smtpd under daemontools inside a vserver and it works fine. Init starts daemontools' svscan which in turns start the 3 qmail services under /services. My setup is mostly the same as the one described in Life With Qmail (http://www.lifewithqmail.org/). No special modification has been required to make it work in a vserver. Cedric Le jeudi 30 mars 2006 à 20:47 +0100, Timothy Arnold a écrit : > Hi All, > > Just wondered if anyone has had any issues starting Qmail inside a vserver > (2.0). I have a straight thing where Qmail will not start on "boot". The > init script does run, but the daemons appear to crash. Once the vserver > has started, I can login and run /etc/init.d/qmail start and it works. > > Some people have suggested that I change init, as I am using the standard > Qmail start/stop script but I think that this might be more fundamental ? > > Is there any easy way to debug the start-up process? > > Thanks! > Tim > > > ___ > Vserver mailing list > Vserver@list.linux-vserver.org > http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Qmail inside vserver 2.0
Hi All, Just wondered if anyone has had any issues starting Qmail inside a vserver (2.0). I have a straight thing where Qmail will not start on "boot". The init script does run, but the daemons appear to crash. Once the vserver has started, I can login and run /etc/init.d/qmail start and it works. Some people have suggested that I change init, as I am using the standard Qmail start/stop script but I think that this might be more fundamental ? Is there any easy way to debug the start-up process? Thanks! Tim ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Re: [parisc 32bit] first test of 'stable' vs 2.6.16-vs2.0.2-rc14 (-pa10 parisc tree)
On Thu, Mar 30, 2006 at 06:23:27PM +0100, Joel Soete wrote: > Hello all, > > given the pb I encountered with ext3 (severall corruption at different places) > with development vs release (2.1...) with this parisc kernel, I try to > implement the stable one (2.0.2). > > Here are the results of test: > Linux patst007 2.6.16-vs2.0.2-rc14-pa10-d32up #5 Thu Mar 30 17:30:05 CEST 2006 > parisc GNU/Linux > Linux-VServer Test [V0.15] Copyright (C) 2003-2006 H.Poetzl > chcontext is working. > chbind is working. > Linux 2.6.16-vs2.0.2-rc14-pa10-d32up #5 Thu Mar 30 17:30:05 CEST 2006 parisc > Ea 0.30.210 263/fallback (S*) > VCI: 0002:0001 263 0316 (TbLgnP) > --- > [000]# succeeded. > [001]# succeeded. > [011]# succeeded. > [031]# succeeded. > [101]# succeeded. > [102]# succeeded. > [201]# succeeded. > [202]# succeeded. > --- > [L01]# succeeded. > [D01]# succeeded. > [L02]# succeeded. > [D02]# succeeded. > [L03]# succeeded. > [D03]# succeeded. > [L11]# succeeded. > [D11]# succeeded. > [L12]# succeeded. > [D12]# succeeded. > [L21]# succeeded. > [D21]# succeeded. > [L22]# succeeded. > [D22]# succeeded. > [L31]# succeeded. > [D31]# succeeded. > Linux-VServer FS Test [V0.13] Copyright (C) 2005-2006 H.Poetzl > Linux 2.6.16-vs2.0.2-rc14-pa10-d32up parisc/0.30.210 > VCI: 0002:0001 263 0316 (ugid24) > --- > testing ext2 filesystem ... > [000]. (ext2 format) > xid related tests ... > [001]. [002]. [011]. [012]. [014]. [015]. [019]. > [020]. [021]. [022]. [023]. [024]. [025]. [026]. [027]. [028]. > [033]. [034]. [035]. [037]. > xattr related tests ... > [101]. [102]. [103]. [104]. [106]. [108]. [109]. > [112]. [113]. [114]. [115]. [116]. [117]. [118]. [119]. > [121]. [122]. [123]. [124]. [199]. > > --- > testing ext3 filesystem ... > [000]. (ext3 format) > xid related tests ... > [001]. [002]. [011]. [012]. [014]. [015]. [019]. > [020]. [021]. [022]. [023]. [024]. [025]. [026]. [027]. [028]. > [033]. [034]. [035]. [037]. > xattr related tests ... > [101]. [102]. [103]. [104]. [106]. [108]. [109]. > [112]. [113]. [114]. [115]. [116]. [117]. [118]. [119]. > [121]. [122]. [123]. [124]. [199]. > > --- > testing xfs filesystem ... > [000]. (xfs format) > xid related tests ... > [001]* > --- > testing reiser filesystem ... > [000]. (reiserfs format) > xid related tests ... > [001]* > --- > testing jfs filesystem ... > [000]. (jfs format) > xid related tests ... > [001]* > <> > > Unfortunately, it's not actualy usable because exhibit to much "BUG: soft > lockup detected on CPU#0!" which dramaticaly reduce the few perf of this box > ;-(. > > It _seems_ to be a parisc kernel pb but not easy to reproduce. Can just hope > ;-) that's a kernel option, you might just want to disable this 'new' feature for now ... thanks, Herbert > Sorry, >Joel > > --- > NOTE! My email address is changing to ... @scarlet.be > Please make the necessary changes in your address book. > > ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Re: Vhashify segmentation fault
[EMAIL PROTECTED] (Herve Guillemet) writes: > There was some mail exchanges some month ago on the list between > Enrico and Alberto about vhashify SIGSEGV on Debian x86_64. How did > this end ? I seem to have the same problem: Does 'make check' report errors for the hashcalc* tests? If so, somebody with an x86_64 and Debian- and beecrypt knowledge should take a look at src/testsuite/hashcalc-plain.c and see what is going wrong there. Enrico pgpyea7Zs5xuR.pgp Description: PGP signature ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] [parisc 32bit] first test of 'stable' vs 2.6.16-vs2.0.2-rc14 (-pa10 parisc tree)
Hello all, given the pb I encountered with ext3 (severall corruption at different places) with development vs release (2.1...) with this parisc kernel, I try to implement the stable one (2.0.2). Here are the results of test: Linux patst007 2.6.16-vs2.0.2-rc14-pa10-d32up #5 Thu Mar 30 17:30:05 CEST 2006 parisc GNU/Linux Linux-VServer Test [V0.15] Copyright (C) 2003-2006 H.Poetzl chcontext is working. chbind is working. Linux 2.6.16-vs2.0.2-rc14-pa10-d32up #5 Thu Mar 30 17:30:05 CEST 2006 parisc Ea 0.30.210 263/fallback (S*) VCI: 0002:0001 263 0316 (TbLgnP) --- [000]# succeeded. [001]# succeeded. [011]# succeeded. [031]# succeeded. [101]# succeeded. [102]# succeeded. [201]# succeeded. [202]# succeeded. --- [L01]# succeeded. [D01]# succeeded. [L02]# succeeded. [D02]# succeeded. [L03]# succeeded. [D03]# succeeded. [L11]# succeeded. [D11]# succeeded. [L12]# succeeded. [D12]# succeeded. [L21]# succeeded. [D21]# succeeded. [L22]# succeeded. [D22]# succeeded. [L31]# succeeded. [D31]# succeeded. Linux-VServer FS Test [V0.13] Copyright (C) 2005-2006 H.Poetzl Linux 2.6.16-vs2.0.2-rc14-pa10-d32up parisc/0.30.210 VCI: 0002:0001 263 0316 (ugid24) --- testing ext2 filesystem ... [000]. (ext2 format) xid related tests ... [001]. [002]. [011]. [012]. [014]. [015]. [019]. [020]. [021]. [022]. [023]. [024]. [025]. [026]. [027]. [028]. [033]. [034]. [035]. [037]. xattr related tests ... [101]. [102]. [103]. [104]. [106]. [108]. [109]. [112]. [113]. [114]. [115]. [116]. [117]. [118]. [119]. [121]. [122]. [123]. [124]. [199]. --- testing ext3 filesystem ... [000]. (ext3 format) xid related tests ... [001]. [002]. [011]. [012]. [014]. [015]. [019]. [020]. [021]. [022]. [023]. [024]. [025]. [026]. [027]. [028]. [033]. [034]. [035]. [037]. xattr related tests ... [101]. [102]. [103]. [104]. [106]. [108]. [109]. [112]. [113]. [114]. [115]. [116]. [117]. [118]. [119]. [121]. [122]. [123]. [124]. [199]. --- testing xfs filesystem ... [000]. (xfs format) xid related tests ... [001]* --- testing reiser filesystem ... [000]. (reiserfs format) xid related tests ... [001]* --- testing jfs filesystem ... [000]. (jfs format) xid related tests ... [001]* <> Unfortunately, it's not actualy usable because exhibit to much "BUG: soft lockup detected on CPU#0!" which dramaticaly reduce the few perf of this box ;-(. It _seems_ to be a parisc kernel pb but not easy to reproduce. Can just hope ;-) Sorry, Joel --- NOTE! My email address is changing to ... @scarlet.be Please make the necessary changes in your address book. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Create a guest
Le 29/03/2006 à 16:39:24+0200, Herbert Poetzl a écrit > On Wed, Mar 29, 2006 at 04:14:11PM +0200, Albert Shih wrote: > > Hi all > > > > Maybe very stupid question, but have a server running FC4 with > > vserver-patch kernel. > > > > I want launch two guest with same version of linux but I don't want > > make a big copy. How can I do that ? > > Where can I find a documentation for make guest with hard-link ? > > vunify and vhashif will do that for you (note: > they will not unfiy with the host fs) > > http://linux-vserver.org/alpha+util-vserver > (check the Directory/vserver unification section) > Well it's seem I'm very stupid man I've install my first vserver succefuly with the documentation on the website. Now I want duplicate my first server to a second server. The only difference between us is the IP number. How can I do that ? You tell me (and Thanks you for that) I can use vunify and mayby vhasif, but I don't understand what's this command do. In the documentation It's describe how can use vunify but not (well my english is not very good) what's he does... Anyone can help me ? Lots of thanks. -- Albert SHIH Universite de Paris 7 (Denis DIDEROT) U.F.R. de Mathematiques. 7 ième étage, plateau D, bureau 10 Heure local/Local time: Thu Mar 30 17:21:07 CEST 2006 ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] bug when starting without daemons
Boris Kolar wrote: Daniel Hokka Zakrisson wrote: Oliver Welter wrote: this is more or less expected behaviour... With recent patches, i.e. 2.0.2-rc11+ or 2.1.0+, you can also set the persistent flag to keep the context around even after all processes die. For util-vserver, this means adding ^38 to the flags file. Is this the default? I now realize it's not a bug, it's a feature ;) But it should be fixed anyway, because if you don't know how vserver works, it can be very puzzling. I disabled all services before my first attempt to start vserver, so I spent quite a few hours to figure out what's going on. No, and it shouldn't be. This is not the behaviour most people expect, and to shutdown such a guest you have to run vattribute --set --xid --flag ~^38, so vserver ... stop is not sufficient. -- Daniel Hokka Zakrisson GPG id: 06723412 GPG fingerprint: A455 4DF3 990A 431F FECA 7947 6136 DDA2 0672 3412 ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] bug when starting without daemons
Daniel Hokka Zakrisson wrote: > Oliver Welter wrote: >> this is more or less expected behaviour... > With recent patches, i.e. 2.0.2-rc11+ or 2.1.0+, you can also set the > persistent flag to keep the context around even after all processes die. > For util-vserver, this means adding ^38 to the flags file. Is this the default? I now realize it's not a bug, it's a feature ;) But it should be fixed anyway, because if you don't know how vserver works, it can be very puzzling. I disabled all services before my first attempt to start vserver, so I spent quite a few hours to figure out what's going on. --- Boris Kolar ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Re: Vhashify segmentation fault
Hello, There was some mail exchanges some month ago on the list between Enrico and Alberto about vhashify SIGSEGV on Debian x86_64. How did this end ? I seem to have the same problem: Linux host 2.6.16-rc5-vs2.1.1-rc12 #3 SMP Thu Mar 16 15:59:40 CET 2006 x86_64 GNU/Linux Debian Sarge host x86_64 Debian Etch guest x86_64 util-vserver-0.30.210 vserver guest hashify -v Initializing exclude-list for /vservers/guest (guest) Starting to traverse directories... skipping '/var' [...] skipping '/proc' Segmentation fault ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
