> experience need only do a "netstat -nap --inet" from the root server when > a vserver it alive... Or atleast, that is all that I do :). Sorry, I haven't been following, you get this oops on 2.4.23rc1 with new vserver and with old vserver? I'm putting together 2.4.23rc1 this week, so far I found one easily fixable kernel panic, I'm using ctx17e, netstat -nap --inet works as expected.
regards, -- Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9 Namagumi namagomi namagoroshi _______________________________________________ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver