Subject: Re: [vserver] Single application per VServer ?
From: Shinkan <shinkan@gmail.com>
Date: Wed, 20 Jan 2010 13:39:35 +0100
Wed, 20 Jan 2010 13:39:35 +0100
Thanks to Corey & Herbert,

vcontext --xid <something> --create -- /etc/init.d/sshd start
works nicely.
Then I can kill it by looking for its pid with
vps aux (is there another way, like filtering by xid ? --help doesn't tell)
and typing
vkill --xid <something> <sshd pid>
(I hoped that "vcontext --xid <same something> --create -- /etc/init.d/sshd
stop" would work but nop ...)

But, I don't really get where it points out.
As it's surprisingly working "out of the box", I'm wondering what is it
doing exactly ?
I mean, it can access every "host" files without any problem... what does
vcontext limit ? Can I tune this ?
What does it bring exactly ?

I tried to read on VServer web site docs, but there's nothing about that.

-- 
Pierre.
"Sometimes when I'm talking, my words can't keep up with my thoughts. I
wonder why we think faster than we speak. Probably so we can think twice." -
Bill Watterson


Thanks to Corey & Herbert,

vcontext --xid <something> --create -- /etc/init.d/sshd start
works nicely.
Then I can kill it by looking for its pid with
vps aux (is there another way, like filtering by xid ? --help doesn't tell)
and typing
vkill --xid <something> <sshd pid>
(I hoped that "vcontext --xid <same something> --create -- /etc/init.d/sshd stop" would work but nop ...)

But, I don't really get where it points out.
As it's surprisingly working "out of the box", I'm wondering what is it doing exactly ?
I mean, it can access every "host" files without any problem... what does vcontext limit ? Can I tune this ?
What does it bring exactly ?

I tried to read on VServer web site docs, but there's nothing about that.

--
Pierre.
"Sometimes when I'm talking, my words can't keep up with my thoughts. I wonder why we think faster than we speak. Probably so we can think twice." - Bill Watterson