Path: utzoo!attcan!nebulus!tslanpar!mslanpar!pat
From: pat@mslanpar (Pat "King of the Trenches" Calhoun)
Newsgroups: comp.bugs.sys5
Subject: Re: ulimit (was: getty/login for callback)
Message-ID: <120@mslanpar>
Date: 20 Apr 89 02:25:02 GMT
References: <180001@mechp10.UUCP> <13853@rpp386.Dallas.TX.US> <797@twwells.uucp> <827@twwells.uucp>
Organization: MSLanpar,Montreal,Quebec
Lines: 33

In article <827@twwells.uucp>, bill@twwells.uucp (T. William Wells) writes:
> This is what I heard, also. But it fails to explain why increasing
> ones ulimit is restricted to root. If ulimit is only a safety belt,
> there isn't any good reason for preventing one from tightening or
> loosening it as needed.
> 

	WARNING: NO SPACE ON DISK 0 PARTITION 0!!! :=)

	In most states, safety belts are not an option. With this in
	mind, it would be useless to have a safety device that could
	be overridden by anyone. This defeats the purpose of having 
	a ulimit.  The message above is not a fantasy, but reality,
	and when it does occur, it's usually a pain to clear out the 
	files (making sure not to get rid of anything of value!)

	To ease the burden of having a low ulimit size as a global 
	default. I have written up new shell which will scan for
	the user's name in a config file which also contains the
	value to be used for that particular user. You might want to
	try this, or modify the 'inittab' entry to look something like
	this:

	ttyxx:nnn:respawn:sh -c 'ulimit nnnn; exec /etc/getty ...'

	This will set the ulimit size for that particular port 
	regardless of the effective user id.


	_^_ |||			Pat "King of the Trenches" Calhoun
       <o o> |			Technical Support Group, Lanpar Technologies
      /\/\/\/\/\	UUCP:   ...!attcan!nebulus!tslanpar!mslanpar
		  DISCLAIMER:   "Read the DAMN manual, I don't need this SHIT!!"