[Vserver] Notification of Limited Account Access (Routing Code:C840-L001-Q190-T1812)
Title: PayPal Billing Dept. Dear PayPal Member, PayPal is committed to maintaining a safe environment for its community of buyers and sellers. To protect the security of your account, PayPal employs some of the most advanced security systems in the world and our anti-fraud teams regularly screen the PayPal system for unusual activity. Recently, our Account Review Team identified some unusual activity in your account. In accordance with PayPal's User Agreement and to ensure that your account has not been compromised, access to your account was flagged. Your account will remain flagged until this issue has been resolved. This is a fraud prevention measure meant to ensure that your account is not compromised. In order to secure your account and quickly restore full access, we may require some specific information from you for the following reason: Our system requires further account verification. Case ID Number: PP-056-245-481 We encourage you to log in and restore full access as soon as possible. Should your account remain flagged for an extended period of time, it may result in further limitations on the use of your account or may result in eventual account closure. - Please click on the link below to log in and restore full access to your account. Click here to activate your account - Thank you for your prompt attention to this matter. Please understand that this is a security measure meant to help protect you and your account. We apologize for any inconvenience. Sincerely, PayPal Account Review Department PayPal Email ID PP562 ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] can't find var/run:
On Sun, Oct 09, 2005 at 07:52:07PM +0200, stefan julius wrote:
> Hello Herbert,
>
> thanx for your help with installation
>
> here a short summary of my questions because my last request was in
> german
> so for all other people who may have the same problems in the future
> (maybe ;-))!
>
>
> My problem was that the vservers directory has been installed
> under/usr/local/etc so
> Herbert informed me to try it with
>
> ./configure --prefix=/usr --sysconfdir=/etc --with-vrootdir=/vservers
>
> and
>
> make install && make install-distribution
>
> all works fine!
>
> For this thanx a lot!
>
> But now there is another directory problem
>
> after installing example DebianSid
>
> (Changing the vserver base path, works fine without any problem, but I
> must say, that I have created the /home/vservers directory manually )
>
> I get everytime the following error message:
>
>
> find: var/run: No such file or directory --> the /var/run directory is
> there, why this message
>
> fakerunlevel: open("/var/run/utmp"): No such file or directory --> the
> utmp file is there, why this message
>
> Failed to start vserver 'DebianSid'
>
>
> after I have commented out the second line in fstab /tmp
>
> fstab:
>
> none /proc procdefaults0 0
> #none /tmptmpfs size=16m,mode=1777 0 0
> none /dev/ptsdevpts gid=5,mode=620 0 0
>
>
>
>
>
> Also after
>
> vserver DebianSid build -m debootstrap -- -d sid -m
> http://ftp.debian.org/debian/pool/main/d/debootstrap/debootstrap_0.1.17.7woody1_i386.deb
> -- --resolve-deps
>
> I mustn't wait for debootstrap to finish.
>
> First I tried as it is described in the step-by-step guide
>
> vserver DebianSid build -m debootstrap -- -d sid -m
> ftp://ftp.at.debian.org/debian/ -- --resolve-deps
>
> Could not find local version of 'debootstrap'; downloading it from
> http://ftp.debian.org/debian/pool/main/d/debootstrap/debootstrap_0.3.1.4_all.deb...
> http://ftp.debian.org/debian/pool/main/d/debootstrap/debootstrap_0.3.1.4_all.deb:
> 21:44:24 FEHLER 404: Not Found.
> ERROR: Could not download the debootstrap package from
>
>/var/tmp/debootstrap.kr2013/debootstrap.deb
>
> Usually, this means that Debian released a new version which is unknown
> to util-vserver and removed the known ones. To fix this, go to
>
>http://ftp.debian.org/debian/pool/main/d/debootstrap/
>
> (or a nearby mirror) and search the URL for the most recent *.deb
> package matching your platform. Then, put this URL into
>
>/etc/vservers/.defaults/apps/debootstrap/uri
>
> and retry the vserver-build command again.
> rm
> -rf /etc/vservers/.defaults/vdirbase/DebianSid /etc/vservers/DebianSid
>
>
> because of this I changed the URL as shown above
>
>
>
> For your information the /var/run/vservers/ and
> the /var/run/vservers.rev /var/run/vservers.help, can be found
> under /usr/var/run/vservers.rev; /usr/var/run/vservers
> and /usr/var/run/vservers.help
> maybe thats the problem I don't know, maybe I shall try
> again ./configure --prefix=/ --sysconfdir=/etc
> --with-vrootdir=/vservers, and not
> --prefix=/usr.
could be, you can also add more specific pathes like
--localstatedir=/var and such, check the final overview
you get _after_ the ./configure, if that suits your
needs ...
HTH,
Herbert
> Maybe it is a simple problem as the other before but I do not come
> further
>
>
> Please help me
>
>
> Greetinx Stefan
>
>
>
>
>
>
>
> ___
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] can't find var/run:
Hello Herbert,
thanx for your help with installation
here a short summary of my questions because my last request was in german
so for all other people who may have the same problems in the future (maybe )!
My problem was that the vservers directory has been installed under/usr/local/etc so
Herbert informed me to try it with
./configure --prefix=/usr --sysconfdir=/etc --with-vrootdir=/vservers
and
make install && make install-distribution
all works fine!
For this thanx a lot!
But now there is another directory problem
after installing example DebianSid
(Changing the vserver base path, works fine without any problem, but I must say, that I have created the /home/vservers directory manually )
I get everytime the following error message:
find: var/run: No such file or directory --> the /var/run directory is there, why this message
fakerunlevel: open("/var/run/utmp"): No such file or directory --> the utmp file is there, why this message
Failed to start vserver 'DebianSid'
after I have commented out the second line in fstab /tmp
fstab:
none /proc proc defaults 0 0
#none /tmp tmpfs size=16m,mode=1777 0 0
none /dev/pts devpts gid=5,mode=620 0 0
Also after
vserver DebianSid build -m debootstrap -- -d sid -m http://ftp.debian.org/debian/pool/main/d/debootstrap/debootstrap_0.1.17.7woody1_i386.deb -- --resolve-deps
I mustn't wait for debootstrap to finish.
First I tried as it is described in the step-by-step guide
vserver DebianSid build -m debootstrap -- -d sid -m ftp://ftp.at.debian.org/debian/ -- --resolve-deps
Could not find local version of 'debootstrap'; downloading it from
http://ftp.debian.org/debian/pool/main/d/debootstrap/debootstrap_0.3.1.4_all.deb...
http://ftp.debian.org/debian/pool/main/d/debootstrap/debootstrap_0.3.1.4_all.deb:
21:44:24 FEHLER 404: Not Found.
ERROR: Could not download the debootstrap package from
/var/tmp/debootstrap.kr2013/debootstrap.deb
Usually, this means that Debian released a new version which is unknown
to util-vserver and removed the known ones. To fix this, go to
http://ftp.debian.org/debian/pool/main/d/debootstrap/
(or a nearby mirror) and search the URL for the most recent *.deb
package matching your platform. Then, put this URL into
/etc/vservers/.defaults/apps/debootstrap/uri
and retry the vserver-build command again.
rm -rf /etc/vservers/.defaults/vdirbase/DebianSid /etc/vservers/DebianSid
because of this I changed the URL as shown above
For your information the /var/run/vservers/ and the /var/run/vservers.rev /var/run/vservers.help, can be found under /usr/var/run/vservers.rev; /usr/var/run/vservers and /usr/var/run/vservers.help
maybe thats the problem I don't know, maybe I shall try again ./configure --prefix=/ --sysconfdir=/etc --with-vrootdir=/vservers, and not
--prefix=/usr.
Maybe it is a simple problem as the other before but I do not come further
Please help me
Greetinx Stefan
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Missing Gentoo init script?
On Sunday 09 October 2005 10:49 am, Herbert Poetzl wrote: > 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) ... > somewhat same with gentoo supplied runlevels are boot and default (runlevel3 in sysv) and yes with a simple needs vprocunhide in the vservers script depends section it would run it if it had not already been 'started'. we were discussing the way i like to work:) instead of naming the marks= to drpepper or something, i could just as easily remove vservers init from the default runlevel until i am done with the work on the host os.. however since i might be manually starting a guest or 2 that i would possibly use for testing or maintenance i would still need vprocunhide to run.. by renaming marks, at least the vservers script runs every boot and will run vprocunhide that way without starting anything else. > 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 Sa
Re: [Vserver] Missing Gentoo init script?
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 > > > > > Vserver@list.linux-vserver.org > > > > > http://list.linux-vserver.org/mailman/listinfo/vserver > > > > > > ___ > > > Vserver mailing list > > > Vserver@list.linux-vserver.org > > > http://list.linux-vserver.org/mailman/listinfo/vserver > ___ > Vserver mailing list > Vserver@l
Re: [Vserver] Missing Gentoo init script?
On Sunday 09 October 2005 08:00 am, Chuck wrote: my mistake! i just looked and it created 2 logs, the 2nd one had the messages :) > On Sunday 09 October 2005 07:13 am, 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... > > > > on a working system when taken down to do some changes its probably easier to > change the default run name than to delete marks in a bunch of servers.. it > can still work i think by changing the default run name from default to > drpepper or something really odd > > > > > > > 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)) > > > > will have to research it when i have more time.. dont need all teh junk it > logs, only need compiler error msgs and the * info messages at the end of > some compiles... i recompiled util-vserver and the info messages were missing > from the log. it had the entire compile history but not the messages.:( > > will research in a few days to see if there is a way to log only msgs and > errors. if i were developing it would be a God-send to have that log, but as > a user, im not interested in anything but messages about special configs, > errors and changes. > > > > > > > > > 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
Re: [Vserver] Missing Gentoo init script?
On Sunday 09 October 2005 07:13 am, 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... > on a working system when taken down to do some changes its probably easier to change the default run name than to delete marks in a bunch of servers.. it can still work i think by changing the default run name from default to drpepper or something really odd > > > > 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)) > will have to research it when i have more time.. dont need all teh junk it logs, only need compiler error msgs and the * info messages at the end of some compiles... i recompiled util-vserver and the info messages were missing from the log. it had the entire compile history but not the messages.:( will research in a few days to see if there is a way to log only msgs and errors. if i were developing it would be a God-send to have that log, but as a user, im not interested in anything but messages about special configs, errors and changes. > > > > > 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 > > > > > Vserver@list.linux-vserver.org > > > > > http://list.linux-vserver.org/mailman/listinfo/vserver > > > > > > _
Re: [Vserver] Missing Gentoo init script?
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... > > 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 > > > > Vserver@list.linux-vserver.org > > > > http://list.linux-vserver.org/mailman/listinfo/vserver > > > > ___ > > Vserver mailing list > > Vserver@list.linux-vserver.org > > http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Missing Gentoo init script?
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:) 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. > 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 > > > Vserver@list.linux-vserver.org > > > http://list.linux-vserver.org/mailman/listinfo/vserver > ___ > Vserver mailing list > Vserver@list.linux-vserver.org > http://list.linux-vserver.org/mailman/listinfo/vserver > -- Chuck "...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. " The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Missing Gentoo init script?
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 > > Vserver@list.linux-vserver.org > > http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
