On Sun, Oct 09, 2005 at 01:13:13PM +0200, Benedikt Boehm wrote: > On Sunday 09 October 2005 12:07, Chuck wrote: > > On Sunday 09 October 2005 03:11 am, Benedikt Boehm wrote: > > > > its just me being lazy not wanting to change the default name to rabbits or > > something in the conf.d config file:) > > well, if you have default marks in your config, you probably want them to > start at boot anyway, else you remove the mark... > > if you don't have any marks configured, the default mark will not start > anything...
at least on sysv based distros, there is something called 'runlevel' and it makes perfect sense there to have vprocunhide run at startup (i.e. in any runlevel) and vserver-legacy or vserver-default (yes there are two different runlevel scripts for that) in just a few of them (e.g. 3,4 or 5) ... also I see no advantage in combining them, as the gentoo dependancy based runlevel script could easily pull the vprocunhide script in, when vserver-default (or legacy) is started, no? just my opinion, I'm not responsible for the gentoo stuff/decisions ... best, Herbert > > it makes perfect sense to put it where it is... the only thing i ask is > > that you change the message after to indicate there are changes and that > > they should remove the vprocunhide from default if it is an upgrade. > > > > possibly one of those beeping timed yellow msgs. :). > > > > i have suggested this several times in bugzilla that they change the way > > portage operates to make it output all info msgs from every pkg emerged to > > a text file with a single msg at the end to check xxx.txt for changes. that > > way people like me who may emerge 10 things and go to bed or out on site > > won't miss anything important. however no one has acted on this in more > > than a year. > > probably you should take a look at PORT_LOGDIR (see make.conf(5)) > > > > > > On Sunday 09 October 2005 02:55, Chuck wrote: > > > > On Saturday 08 October 2005 08:01 pm, Benedikt Boehm wrote: > > > > > > > > > > > > its a good place to put it when you use the vservers init script to > > > > auto start. but when you dont there is no option to call vservers > > > > unhide or some such to just run vprocunhide... i know i can set all > > > > the guests to some mark other than default or change the default to > > > > some other name, but when working on the systems its a pain to keep > > > > editing back and forth so vservers doesnt find anything to start.. > > > > > > > > please realize this is my own uneducated opinion, but i still vote for > > > > a separatre script. for me the way i work and use them its far more > > > > convenient. > > > > > > the vservers init script does only start those guests you tell it to, if > > > you don't specify any guest it will just make proc entries visible.. > > > > > > additionally the vservers init script ensures that on stop/reboot _all_ > > > > guests > > > > > are shut down probperly > > > > > > so there is definitely no need to put one command (vprocunhide) in an > > > extra ini script. > > > > > > > i just re-emerged util-vserver-0.30.208-r3 to see the msg that i > > > > missed... > > > > > > it doesnt tell me that vprocunhide is no longer a separate script. it > > > > tells > > > > > > me to run vprocunhide then goes on to tell me an init script was > > > > installed and how to add it with no reference that vprocunhide was > > > > added into it.. there is nothing about changes.. sorry:) > > > > > > > > * You have to run the vprocunhide command after every reboot > > > > * in order to setup /proc permissions correctly for vserver > > > > * use. An init script has been installed by this package. > > > > * To use it you should add it to a runlevel: > > > > * > > > > * rc-update add vserver default > > > > * > > > > * This init script will also help you to start/stop your vservers > > > > * on reboot. See /etc/conf.d/vserver for details > > > > > > what nice message! it told you everything i told you :) > > > > > > > > On Saturday 08 October 2005 22:19, Chuck wrote: > > > > > > It appears that the ebuild for util-vserver-0.30.208-r3 is missing > > > > > > the vprocunhide init script. On a clean system it did not install > > > > > > one and > > > > I > > > > > > > > could not find one. I copied one from another host. > > > > > > > > > > you should read the messages popping up after the build of > > > > > util-vserver > > > > > > > > > > the two init scripts (vprocunhide and vservers) have been merged into > > > > one > > > > > > > (vservers) > > > > > _______________________________________________ > > > > > Vserver mailing list > > > > > [email protected] > > > > > http://list.linux-vserver.org/mailman/listinfo/vserver > > > > > > _______________________________________________ > > > Vserver mailing list > > > [email protected] > > > http://list.linux-vserver.org/mailman/listinfo/vserver > _______________________________________________ > Vserver mailing list > [email protected] > http://list.linux-vserver.org/mailman/listinfo/vserver _______________________________________________ Vserver mailing list [email protected] http://list.linux-vserver.org/mailman/listinfo/vserver
