From: Thomas Guettler (hv_at_tbz-pariv.de)
Date: Thu 18 Mar 2004 - 14:21:56 GMT
Am Donnerstag, 18. März 2004 13:26 schrieb bogdan_at_llama.fdns.net:
> 1) There 2 unknown context with no names.
> 2) Still can't stop any vservers
> wptop:~/src# vserver-stat
> CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME DESCRIPTION
> 0 363 3GB 1MB 4h00m59 52m43.93 497d02h27 root server
> 49152 7 12MB 515B m00.56 m00.66 497d02h08 EXCHANGE exchange
> ns3.fuzzitech.net
> 49153 23 62MB 5kB m02.93 m06.27 497d02h08
> 49154 3 4MB 356B m00.16 m00.24 497d02h08 ALTERNC alternc
> test server
> 49157 4 5MB 242B m00.04 m00.08 496d10h14
> 49158 4 5MB 210B m00.04 m00.05 496d10h12
> 49159 2 3MB 222B m01.27 m02.22 496d09h24 WPTOP
> 49160 10 57MB 7kB m02.55 m01.05 496d03h41 FWD
> wptop:~/src# vserver FWD stop
> Stopping the virtual server FWD
> Error: /proc must be mounted
> To mount /proc at boot you need an /etc/fstab line like:
> /proc /proc proc defaults
> In the meantime, mount /proc /proc -t proc
Hi,
You can stop the vserver by hand:
"chcontext --ctx" and kill all processes.
The error message that proc is not mounted is
missleading. Some files in /proc are not visible.
You can change the visibility with vproc. Up to now
I don't know which file in /proc produces this error.
HTH,
Thomas
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver