---------- Forwarded message ----------
Date: Wed, 24 Dec 97 02:22:47 +0200
From: MAILER-DAEMON@gate.wim.net
To: yuri@killer.cracksoft.kiev.ua
Subject: failure notice
Hi. This is the qmail-send program at gate.wim.net.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<wriede@linnie.wim.net>:
Sorry, I couldn't find any host named linnie.wim.net. (#5.1.2)
- --- Below this line is a copy of the message.
Return-Path: <yuri@killer.cracksoft.kiev.ua>
Received: (qmail 17202 invoked by alias); 24 Dec 1997 00:22:29 -0000
Delivered-To: wriede@gate.wim.net
Received: (qmail 17145 invoked from network); 24 Dec 1997 00:22:17 -0000
Received: from localhost (HELO mail.monmouth.com) (root@127.0.0.1)
by localhost with SMTP; 24 Dec 1997 00:22:16 -0000
Received: from nic.funet.fi (nic.funet.fi [128.214.248.6]) by
shell.monmouth.com (8.8.5/8.7.3) with ESMTP id RAA09134 for
<wriede@monmouth.com>; Sun, 21 Dec 1997 17:26:21 -0500 (EST)
Received: from vger.rutgers.edu ([128.6.190.2]:16144 "EHLO vger.rutgers.edu"
ident: "root") by nic.funet.fi with ESMTP id <16032-627>; Mon, 22 Dec 1997
00:25:23 +0200
Received: by vger.rutgers.edu id <971046-6776>; Sun, 21 Dec 1997 15:03:34 -0500
Received: from cs.cracksoft.kiev.ua ([195.5.17.106]:1459 "EHLO
cs.cracksoft.kiev.ua" ident: "NO-IDENT-SERVICE") by vger.rutgers.edu with ESMTP
id <971043-6773>; Sun, 21 Dec 1997 15:03:24 -0500
Received: (from fido@localhost)
by cs.cracksoft.kiev.ua (8.8.8/8.8.8) id WAA16499
for linux-kernel@vger.rutgers.edu; Sun, 21 Dec 1997 22:08:13 +0200
X-Authentication-Warning: cs.cracksoft.kiev.ua: fido set sender to
Yuri.Kuzmenko@f169.n463.z2.fidonet.org using -f
Received: from f169.n463.z2.fidonet.org by f257.n463.z2.fidonet.org
with FTN (ifmail v.2.12.os) id AA16497; Sun, 21 Dec 97 22:08:12 +0200
Apparently-To: linux-kernel@vger.rutgers.edu
To: linux-kernel@vger.rutgers.edu
From: Yuri Kuzmenko <yuri@killer.cracksoft.kiev.ua>
X-FTN-Sender: Yuri Kuzmenko <Yuri.Kuzmenko@f169.n463.z2.fidonet.org>
Reply-To: yuri@killer.cracksoft.kiev.ua
Date: Sun, 21 Dec 97 22:05:22 +0200
Subject: ___ some stability proposal
Message-ID: <199712212005.WAA04375@killer.cracksoft.kiev.ua>
X-FTN-FLAGS: PVT K/S
X-FTN-MSGID: 2:463/169@fidonet 5cf89053
X-FTN-REPLYADDR: yuri@killer.cracksoft.kiev.ua
X-FTN-REPLYTO: 2:463/169@fidonet UUCP
X-FTN-Via: ifmail 2:463/169@fidonet, Sun Dec 21 1997 at 22:05 (2.12.os)
X-Orcpt: rfc822;linux-kernel@vger.rutgers.edu
Sender: owner-linux-kernel@vger.rutgers.edu
Precedence: bulk
I have the small proposal for Linux-IPC. The fact is that I have try to create
the _stable_ system for "bad" users. ulimit (for limit the memory size and cpu
time) is good, but not works for IPC shared memory allocating (shmget()). In
result, programm below allocates 100mb of memory, and system can't work
further. I offer to make ulimit-like routines for shared-memory or simple
register procfs elements like as /etc/hosts.allow and /etc/hosts.deny (for
this, there is lists of allowed/disabled uids for shmget syscall).
Also I have small question about RLIMIT_CPU. I want to limit CPU-load for the
given user. But RLIMIT_CPU limit only *time* in seconds. Maybe needed to make
addition to sheduler for limit the summary of all realtime/cputime for given
user?
/* ipcsuck.c */
#include <sys/ipc.h>
#include <sys/shm.h>
#include <string.h>
void main()
{
int i; char *p;
for(i=0;i<100;i++)
{
p=shmat(shmget(0,1024*1024,IPC_CREAT|IPC_PRIVATE|0666),NULL,0);
memset(p,0,1024*1024);
}
}