1) There 2 unknown context with no names.
2) Still can't stop any vservers
wptop:~/src# vserver-stat
CTX PROCVSZRSS userTIME sysTIMEUPTIME NAME DESCRIPTION
0 3633GB1MB 4h00m59 52m43.93 497d02h27 root server
491527 12MB 515Bm00.56m00.66 497d02h08 EX
Hi,
I have troubles with the default capabilities of chcontext.
varchiv is virtual, here CAP_SYS_CHROOT is enabled:
varchiv:~ # grep s_context /proc/self/status
s_context: 49176
varchiv:~ # reducecap --show | grep -i chroot
CAP_SYS_CHROOT X X
If I start a new context, I have
Am Donnerstag, 18. März 2004 13:26 schrieb [EMAIL PROTECTED]:
> 1) There 2 unknown context with no names.
> 2) Still can't stop any vservers
> wptop:~/src# vserver-stat
> CTX PROCVSZRSS userTIME sysTIMEUPTIME NAME DESCRIPTION
> 0 3633GB1MB 4h00m59 52m43.93 497d02h
I installed sendmail on a debian-linux-server running "vserver" several
times,
on each vserver one sendmail. The idea is that the vserver mail2 gets
mail from outside and delivers it to another vserver where the local
users are.
Because vservers are installed, I have to avoid 127.0.0.1, all mails
[EMAIL PROTECTED] (Thomas Guettler) writes:
> If you use "--cap CAP_NET_RAW" with chcontext chroot is not possible.
I know about miscompilations with SuSE 9 (gcc 3.3.1). Can you try the
'-O0' flag and see if problem still exists?
> - util-vserver-0.29.3/NEWS:
> Version 0.30 --> What is it?
[EMAIL PROTECTED] (Thomas Guettler) writes:
> - Introduction at http://dns.solucorp.qc.ca/miscprj/s_context.hc
>has some old parts.
>- newvserver does not exist (I think you use "vserver foo build"
> now)
You need the -linuxconf subpackage; but it is deprecated.
> - Is there a too
On Thu, Mar 18, 2004 at 03:16:25PM +0100, Thomas Guettler wrote:
> Hi,
Hi Thomas!
first, let me say that I appreciate your constructive
criticism, and the new-user testing (please don't get me
wrong here) is the perfect way to improve in this regard
> I have troubles with the default capabilitie
Hello, congratulations and many thanks for the vserver-project, I like
it really.On my home-server I'm running a linux-2.4.23 with the vserver patch
without any problems, but on my webserver I've found really strange
things happend last night.Its an Athlon Duron System with 1800Mhz and 128MB of 266
I found the solution, there is a submit.cf for sendmail being used when
sendmails gets invoked like this:
sendmail -v [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
On Thu, Mar 18, 2004 at 05:36:20PM +0100, Andreas Reck wrote:
> Hello, congratulations and many thanks for the vserver-project, I like
> it really.On my home-server I'm running a linux-2.4.23 with the vserver patch
> without any problems, but on my webserver I've found really strange
> things happe
Just to clarify - this is only a problem for the sendmail running on the
main (ctx 0) server, correct?
Grisha
On Thu, 18 Mar 2004, Stadt Zirndorf, EDV wrote:
> I found the solution, there is a submit.cf for sendmail being used when
> sendmails gets invoked like this:
>
> sendmail -v [EMAIL PRO
Is there a way to preserve the cq hash across reboots?
I saw the script that someone e-mail that preserves the amount of space
available, but what about the hash itself?
Otherwise it looks like if you delete any files that you created prior to
reboot you don't gain any space back.
Or am I missi
On Thu, Mar 18, 2004 at 04:08:43PM -0500, Gregory (Grisha) Trubetskoy wrote:
>
> Is there a way to preserve the cq hash across reboots?
>
> I saw the script that someone e-mail that preserves the amount of space
> available, but what about the hash itself?
>
> Otherwise it looks like if you dele
On Thu, 18 Mar 2004, Herbert Poetzl wrote:
> saving the 'current' value on vserver stop and restoring it on vserver
> start should be sufficient ...
I guess I'm confused as to whether mounting the filesystem with tagctx is
sufficient. I'm on 1.26 (so I don't have lsxid), and I was following
inst
> Hello Herbert,
>
> Am Don, den 18.03.2004 schrieb Herbert Poetzl um 18:25:
>
> > see http://lkml.org/lkml/2004/3/3/180
> > (guess it's a rare bug() not found/fixed yet)
> >
> yea that's the thread I've meant, after reading this I decided to
> downgrade to linux-2.4.24 again. Just wondered be
OK, I figured it out.
I guess it really helps not to have CONFIG_INOXID_NONE in the kernel
config. (Or in other words "Persistent Context ID for files" options in
make menuconfig).
Sorry for the confusion!
Grisha
On Thu, 18 Mar 2004, Herbert Poetzl wrote:
> On Thu, Mar 18, 2004 at 04:08:43PM
On Thu, Mar 18, 2004 at 07:07:45PM -0500, Gregory (Grisha) Trubetskoy wrote:
>
> OK, I figured it out.
>
> I guess it really helps not to have CONFIG_INOXID_NONE in the kernel
> config. (Or in other words "Persistent Context ID for files" options in
> make menuconfig).
LOL!
> Sorry for the conf
No, this configuration hint is valid for all vservers _and_ the main server.
Greetings,
Richard
--
Stadt Zirndorf, EDV
Richard Lippmann
Tel. 0911/9600-190
-Ursprüngliche Nachricht-
Von: Gregory (Grisha) Trubetskoy [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 18. März 2004 20:56
An:
18 matches
Mail list logo