basically , in a nutshell, YOU NAILED IT!! IT WORKS!!!
it auto-starts the guests like it should.
first boot, after a few min i manually stopped each guest. no errors.
rebooted , no errors on shutdown.
after about 10 min of guests running, i just rebooted letting the runlevel
shut the vservers down like it is supposed to..
it shut them down with no errors however, this showed up just after shutting
down the last one:
Stopping single vserver: ns ) ... [ ok ]
basename: too many arguments
nothing else after that except advising to type basename --help and it
proceeded to do a flawless reboot.
the only thing i need to do now, is let it run a day and try a reboot tomorrow
night again to see what it does after the system has had a chance to get
and i want to find out why this one guest shows me all its init messages on
startup or shutdown. it started after a particularly bad crash shutting down
the other day. none of the other guests do it so its tied in with this one
guest. any place i can look? maybe a >null that cancels these msgs got messed
outside of that basename error and the init msgs being shown to the screen on
the one guest, it appears to be flawless. except i noticed one thing in
looking over the boot log:
very early in the startup:
Oct 5 01:10:32 apollo syslogd 1.4.1: restart.
Oct 5 01:10:33 apollo kernel: klogd 1.4.1, log source = /proc/kmsg started.
Oct 5 01:10:33 apollo kernel: Cannot find map file.
Oct 5 01:10:33 apollo kernel: Error querying loaded modules - Function not
Oct 5 01:10:33 apollo kernel: Linux version 220.127.116.11-vs2.1.0-rc3
(root@apollo) (gcc version 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7$
Oct 5 01:10:33 apollo kernel: BIOS-provided physical RAM map:
cannot find map file.. the map file is there.. and when i made the kernel i
did the usual make then make install then make modules_install. i have no
modules loaded, however i did make sensor modules to load in the future in
planning to monitor temps and fans remotely.
lrwxrwxrwx 1 root root 31 Oct 5 00:41 System.map ->
-rw-r--r-- 1 root root 898942 Oct 5 00:41 System.map-18.104.22.168-vs2.1.0-rc3
maybe this error has been there before and i just never noticed it? usually i
dont examine the boot this closely, if it works, it works:)
now the only thing i wonder is if something in the debug code is making it
work right, and will it still work with debugging shut off?... maybe will get
adventurous and try that tomorrow night. i cant imagine debug stuff on not
having an impact on performance.
-- Chuck _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserverReceived on Wed Oct 5 06:43:04 2005