On Thu, 24 Jun 2004 [EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] root]# vserver test start
> Starting the virtual server test
> Server test is not running
> ipv4root is now 192.168.1.14
> New security context is 49159
> [EMAIL PROTECTED] root]#
Did you expect something else to happen. Try vserver-stat and see if it
is or isn't actually running.
On one of my older systems I see:
CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME DESCRIPTION
0 31 30MB 2kB 3d06h41 1d02h52 147d04h08 root server
22 13 82MB 6kB 9m59.71 3m59.74 147d04h05 db2
100 10 36MB 2kB 1m42.41 m51.42 34d09h38 da2
101 13 167MB 23kB 14d09h59 6m49.03 147d03h47 rt
200 8 137MB 2kB 8m59.84 7m41.26 147d04h05 mydb2
This shows four vservers plus the root server running.
Then to access the 'rt' vserver I would use the command
vserver rt enter
and see:
ipv4root is now 192.168.3.101
New security context is 101
Kernel do not support chrootsafe(), using chroot()
[EMAIL PROTECTED]
{/}#
(And yes it is a really old system but running strong enough to wait for
update when my new(/used) 4-way Xeon system becomes available. And
perhaps vserver for the 2.6 kernel will be super stable also :-)
HTH,
Rod
--
"Open Source Software - You usually get more than you pay for..."
"Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"
_______________________________________________
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver
