home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.sysadmin
- Path: sparky!uunet!cs.utexas.edu!sdd.hp.com!wupost!mont!mizzou1.missouri.edu!CCGREG
- From: CCGREG@mizzou1.missouri.edu (Greg Johnson)
- Subject: Re: changing login tiff --- where is it in 3.0 ?
- Message-ID: <1685ECA3D.CCGREG@mizzou1.missouri.edu>
- Sender: news@mont.cs.missouri.edu
- Nntp-Posting-Host: mizzou1.missouri.edu
- Organization: University of Missouri
- References: <1992Sep6.165513.11989@ni.umd.edu> <1992Sep8.205020.11252@menudo.uh.edu>
- Date: Thu, 10 Sep 92 14:22:40 CDT
- Lines: 19
-
- In article <1992Sep8.205020.11252@menudo.uh.edu>
- sears@tree.egr.uh.edu (Paul S. Sears) writes:
- >What surprises me is that noone uses the /etc/ttys file. No need to dwrite to
- >the defaults database (which gets hosed every so often...)
-
- Yes, I felt the same way until recently when I tried to specify ALL
- the loginwindow options via the ttys file. There seems to be some
- limit on the length of that options string, around 128 characters. I
- didn't properly investigate it, since there was an alternative. I
- simply specify at least the LoginHook in ttys, then in the LoginHook
- program dwrite the other options. The LoginHook runs as root and
- propagates any change throughough the network.
-
- Another thing I do with LoginHook is create a standard user home
- directory if it doesn't exist. This saves allocating 300K per user
- until they actually login. Modify nu.cf or nulib/nu1.sh &
- nulib/nu2.sh to not allocate home dirs. This is particularly useful
- since we purge most user homes anyway at the end of each semester,
- as part of standard policy.
-