From: Alex Lyashkov (shadow_at_psoft.net)
Date: Wed 26 Nov 2003 - 07:11:31 GMT
On Wednesday 26 November 2003 07:50, Charles Dale wrote:
> It's a bit hard to read what you posted because after a certain point all
> the hard returns seem to have been folded. But I think you have this in
> your redhat9.conf:
>
> S_CAPS="CAP_NET_RAW CAP_SYS_ADMIN CAP_NET_ADMIN"
>
> Change that to
>
> S_CAPS="CAP_NET_RAW CAP_SYS_RESOURCE"
>
stop use CAP_SYS_RESOURCE in vserver, because you process limit be broken.
part from linux-vserver-1.1.2:
==================================================
iff -NurpP --minimal linux-2.4.21/kernel/fork.c
linux-2.4.21-vs1.1.2/kernel/fork.c
--- linux-2.4.21/kernel/fork.c Fri Jun 13 16:51:39 2003
+++ linux-2.4.21-vs1.1.2/kernel/fork.c Fri Nov 14 03:35:40 2003
@@ -22,6 +22,7 @@
#include <linux/namespace.h>
#include <linux/personality.h>
#include <linux/compiler.h>
+#include <linux/vcontext.h>
#include <asm/pgtable.h>
#include <asm/pgalloc.h>
@@ -629,6 +630,10 @@ int do_fork(unsigned long clone_flags, u
*p = *current;
retval = -EAGAIN;
+ if (p->s_info && (p->s_info->flags & VX_INFO_NPROC)) {
+ if (atomic_read(&p->s_info->refcount) >=
p->rlim[RLIMIT_NPROC].rlim_max)
+ goto bad_fork_free;
+ }
==================================================
Herber rewrite it for work with internaly rlimits array.
-- With best regards, Alex _______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver