🚀 go-pugleaf

In article <697@occrsh.ATT.COM> rjd@occrsh.UUCP (Randy_Davis) writes:
>
>  Wrong - all of these schemes to change the ulimit BEFORE the login program
>is run from the normal sequence init-getty-login-shell will not work!!!
>
>  If the ulimit is set to some high number before login is run (and, in fact it
>IS), such as in the kernel, and if you are running a System V version before the
>ulimit was settable in the /etc/master.d/kernel file, the ulimit for logins is
>last set in the /bin/login program.  So, setting your kernel, your init, or
>your getty ulimit higher would be fine, yet as soon as a person logs in and
>run this (pre-3.0) /bin/login, the line "ulimit(2,<low number>);" (near line
>248 in the source if you are curious) would be implemented for all non-root
>logins, and you are back to where you started.

I have a System V.2 source licence direct from AT&T. I examined the
source to login and found that this just was *not* true. I don't know
what version you are looking at but the System V.2 version of login that
your company distributed does not have any reference to ulimit in it 
anywhere.

The ulimit for users is initially set in uts/machine/os/main.c with a 
line like: 
u.u_limit = CDLIMIT;

There are NO references to ulimit in V.2 init, V.2 getty or V.2 login. 
The wrapper ideas *can* work, *do* work, and *are* working at a number 
of sites that I know about. This is a kludge to get around a "feeeature"
that in my opinion is more trouble than its worth.

>Randy Davis					UUCP: ...(att!)ocrjd!randy

This sounds like a CM problem to me.. Which Version, What Version, 
Whose's Version, Your Version. :-)

			-Kent+
---
Kent Landfield               UUCP:     kent@ssbell
Sterling Software FSG/IMD    INTERNET: kent%ssbell.uucp@uunet.uu.net
1404 Ft. Crook Rd. South     Phone:    (402) 291-8300 
Bellevue, NE. 68005-2969     FAX:      (402) 291-4362