Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site mtung.UUCP
Path: utzoo!decvax!bellcore!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!akgua!akguc!mtunh!mtung!pgf
From: pgf@mtung.UUCP (Paul Fox)
Newsgroups: net.micro.att
Subject: running ksh on the UNIX pc
Message-ID: <672@mtung.UUCP>
Date: Wed, 12-Feb-86 14:27:40 EST
Article-I.D.: mtung.672
Posted: Wed Feb 12 14:27:40 1986
Date-Received: Fri, 14-Feb-86 00:33:06 EST
Distribution: na
Organization: AT&T ISL Holmdel NJ USA
Lines: 31
Xref: mtunh net.micro.att:813 att.micro:462



	Since I believe ksh is available from THE STORE, I figured I'd
	post a couple of tips we've discovered on installing it.

	First, *don't* call (or link it to) /bin/sh.  A lot of shell scripts
	run slightly differently under ksh, and the disruption caused to 
	User Agent utilities is not worth it.  You should make it your 
	default shell by adding the appropriate entry to /etc/passwd.

	You may also make it the default shell for root and install in this
	manner.  However...  if you have made it the default shell to be 
	used by root (as the last entry in /etc/passwd), then you should 
	know that any /usr/lib/crontab entries which do an "su root" will 
	no longer run.  One consequence of this is that since /etc/cleanup.wk 
	will never run, then /usr/adm/cronlog and /usr/adm/sulog will grow 
	forever.  (Mine combined were almost a megabyte after a month or two.)  

	The fix is to provide another login in /etc/passwd, called, say,
	"cronroot", with a password of "NONE", uid and gid of 0, and
	no entry for default shell.  Then change any lines in crontab that
	do an "su root" to "su cronroot". 

	I suppose this may affect applications which put such entries into 
	crontab, but that may be the price of ksh...

			Paul Fox, AT&T Information Systems, Holmdel NJ.
			  [ihnp4|vax135]!mtung!pgf (201)834-3740
-- 
			Paul Fox, AT&T Information Systems, Holmdel NJ.
			  [ihnp4|vax135]!mtung!pgf (201)834-3740