Chuck wrote:
>On Monday 19 September 2005 02:51 am, Tor Rune Skoglund wrote:
>
>very interesting. thanks for that link! i think you are right. i didn't want
>to play with scripts that were supplied just to be sure I didn't create some
>error of my own witthout consulting someone first.
>
>
>
No problem, but still it for me it doesn't stop correctly. It is just
being killed after a
timeout. Do you have the same problem? I presume this might be something
to do
with the Gentoo 'version' of vserver, as I have not seem anyone else
report that.
Tor Rune Skoglund
>>Chuck wrote:
>>
>>
>>
>>>btw this is a gentoo system and the vserver host and template install were
>>>according to the hollow how-to, and i manually cloned the guests from the
>>>template by first using hollow's instructions to create a skeleton then
>>>
>>>
>doing
>
>
>>>cp -al template/* guest
>>>
>>>then running
>>>
>>>find guest -type f -exec setattr --iunlink {} ';'
>>>
>>>then i go in and edit configs. the lnkage breaking works fine it seems.
>>>
>>>so then back to the problem, in the 2 i want autostarted, i placed a mark
>>>
>>>
>file
>
>
>>>in there with the contents of a single line that said
>>>
>>>default
>>>
>>>then i put a mark file into my template with a single line
>>>
>>>nostart
>>>
>>>now it starts them properly
>>>
>>>however, shutdown by /etc/init.d/vservers stop
>>>
>>>has an instant return and the guests are still running and continue to do
>>>
>>>
>so.
>
>
>>>i have to shut them down with vserver guest stop then it times out as it
>>>
>>>
>has
>
>
>>>been and stops the guest. so for the heck of it i removed the mark files
>>>completely and the init script starts all and shuts down all properly but
>>>
>>>
>it
>
>
>>>includes my template.
>>>
>>>confused... im about to put the veserver guest start commands into my local
>>>startup file and the stop command into the local stop file
>>>
>>>any clues why the init would return immediately and basically do nothing on
>>>stop? after i stop them with vserver util, i run the iniot with vstatus
>>>
>>>
>and
>
>
>>>it still shows that servers are running of type default.
>>>
>>>
>>>
>>>
>>>
>>I experienced the same. Might be this bug:
>>
>>http://savannah.nongnu.org/bugs/?func=detailitem&item_id=14525
>>
>>Editing the init-script to stop vservers of just type default might help
>>for you too.
>>
>>
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
