Hi Dariush, Old vserver for me is fine (2.4.22 + c17). Wanted to make up a new kernel, saw this new branch of Vserver with 2.4.23-rc1 patches ready to go, so went that route :).
I also patched in/ turned on the realtime kernel. It patched clean, but hey, who knows ;(. But the Oops suggests it's network. JES On Tue, 18 Nov 2003, Dariush Pietrzak wrote: > > 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, > -- James B. MacLean [EMAIL PROTECTED] Department of Education Nova Scotia, Canada B3M 4B2 _______________________________________________ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver