Hi, I am seeing this same behaviour with 2.4.24-vs1.3.4:
[EMAIL PROTECTED]:~]vserver swapoff enter -su: fork: Resource temporarily unavailable -su-2.05b# The same config worked fine with vs1.22. Regards, Alec > supported in 1.3.x. So I didn't tested it extensive. > A vanilla 2.4.23 with patch-2.4.23-vs1.3.1.diff and vserver-0.29 gave me > a runing system but trying to start my vservers results in: > > Starting the virtual servers > Starting the virtual server v101 > Server v101 is not running > ipv4root is now 192.168.74.101 > Host name is now v101 > New security context is 49156 > /usr/lib/vserver/save_s_context: fork: Resource temporarily unavailable > Starting the virtual server v102 > Server v102 is not running > ipv4root is now 192.168.74.102 > Host name is now v102 > New security context is 49157 > /usr/lib/vserver/save_s_context: fork: Resource temporarily unavailable > > -rwxr-xr-x 1 root root 322 Dec 25 21:19 > /usr/lib/vserver/save_s_context > > A problem on my side? > > -- > No�l K�the <noel debian.org> > Debian GNU/Linux, www.debian.org -- Evolution: Taking care of those too stupid to take care of themselves. _______________________________________________ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
