Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.Hawaii.Edu!news.caldera.com!enews.sgi.com!nntprelay.mathworks.com!howland.erols.net!newsfeed.nacamar.de!peernews.ftech.net!Aladdin!aladdin.net!ns2.aladdin.net!RMplc!rmplc.co.uk!yama.mcc.ac.uk!news.york.ac.uk!pih100
From: pih100@york.ac.uk (Paul Halliday)
Newsgroups: comp.unix.pc-clone.32bit,comp.unix.bsd.freebsd.misc,comp.unix.bsd.386bsd.misc,comp.os.ms-windows.nt.advocacy,comp.os.linux.x,comp.os.linux.setup,comp.os.linux.advocacy
Subject: Re: Linux needs more work to be done!
Followup-To: comp.unix.pc-clone.32bit,comp.unix.bsd.freebsd.misc,comp.unix.bsd.386bsd.misc,comp.os.ms-windows.nt.advocacy,comp.os.linux.x,comp.os.linux.setup,comp.os.linux.advocacy
Date: 9 Jul 1997 18:17:14 GMT
Organization: The University of York, UK
Lines: 22
Sender: pih100@york.ac.uk
Message-ID: <5q0kja$4ni$1@netty.york.ac.uk>
References: <5oqbad$1582@ds2.acs.ucalgary.ca> <xdoradosk1v.fsf@bagel.rs.itd.umich.edu> <xdo4taj2akk.fsf@pita.ccs.itd.umich.edu> <5peb7i$aqv$1@netty.york.ac.uk> <pkuip5.tq.ln@zen>
NNTP-Posting-Host: tower.york.ac.uk
X-Newsreader: TIN [version 1.2 PL2]
Xref: euryale.cc.adfa.oz.au comp.unix.pc-clone.32bit:9728 comp.unix.bsd.freebsd.misc:44180 comp.unix.bsd.386bsd.misc:1311 comp.os.ms-windows.nt.advocacy:65361 comp.os.linux.x:66170 comp.os.linux.setup:120470 comp.os.linux.advocacy:104921
Robert Brockway (robert@zen.humbug.org.au) wrote:
: Paul Halliday (pih100@york.ac.uk) wrote:
: : Is this the same effect as running several callocs in an infinite loop?
: : e.g. For simplicity;
: : main() { for(;;) calloc(10000, 8); }
: Checkout limit or ulimit (depending on your shell). Look particluarly at
: memory limits. This is an old trick. Any half decent setup unix won't
: notice it once forking stops when the process limit is hit :-)
: Ergo, process limits are good too.
Cheers for the suggestion (and also to the two people that emailed me
also suggesting the same thing :) - but how could one set a resource limit
on Linux when used as a central Uni× server where a user might wish to log
in with their own shell - perhaps even with the malicious intention of
bringing the machine down? Are there similar limits one can set in the
kernel?
I know one could force them to use a certain parent shell which has
process limits, but this seems a little silly (esp. since some other
unices don't need to do it this way) ...
Thanks,
Paul.