Le Jeudi 14 Avril 2005 00:42, Herbert Poetzl a �crit�: > > Well I recompiled with debugging support, but I do not get > > messages... Is there a command to actually enable it (Like "echo 1 > > > /proc/..."), or a particular file to look for ? > > yep, you enable the debug messages (most are bit coded) > by writing the resulting number to one of the > /proc/sys/vserver/debug_* entries ... > > for example 'echo 255 >/proc/sys/vserver/debug_switch' > will enable debugging for the syscall switch ...
That worked, ok. So, now, I'm trying to set all the capabilities to know whether my problem comes from a lack of it... I write these lines in "/etc/vservers/vs5/bcapabilities" : # cat bcapabilities CHOWN DAC_OVERRIDE DAC_READ_SEARCH FOWNER FSETID KILL SETGID SETUID SETPCAP LINUX_IMMUTABLE NET_BIND_SERVICE NET_BROADCAST NET_ADMIN NET_RAW IPC_LOCK IPC_OWNER SYS_MODULE SYS_RAWIO SYS_CHROOT SYS_PTRACE SYS_PACCT SYS_ADMIN SYS_BOOT SYS_NICE SYS_RESOURCE SYS_TIME SYS_TTY_CONFIG MKNOD LEASE QUOTACTL Is it the right way to do it ? What about "ccapabilities" ? -- ,, (�> Nicolas Costes /|\ IUT de La Roche / Yon ( ^ ) Cl� publique: http://www.keyserver.net/ ^ ^ Musique libre: http://www.magnatune.com/
pgpFGkH3xG5aO.pgp
Description: PGP signature
_______________________________________________ Vserver mailing list [email protected] http://list.linux-vserver.org/mailman/listinfo/vserver
