Xref: utzoo unix-pc.general:131 comp.sys.att:1984 comp.unix.questions:4949 comp.unix.wizards:5968
Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!ames!hao!noao!rutgers!ho95e!homxb!ho7cad!wjc
From: wjc@ho5cad.ATT.COM
Newsgroups: unix-pc.general,comp.sys.att,comp.unix.questions,comp.unix.wizards
Subject: Re: Non-standard shell and su.
Message-ID: <264@ho7cad.ATT.COM>
Date: 4 Jan 88 14:40:18 GMT
References: <200@icus.UUCP>
Sender: nuucp@ho7cad.ATT.COM
Lines: 21
In-reply-to: lenny@icus.UUCP's message of 3 Jan 88 06:12:26 GMT


In article <200@icus.UUCP> lenny@icus.UUCP (Lenny Tropiano) writes:
>  [su with "-c" problem described]
>   Does the "-c" option only work with the Bourne shell (/bin/sh)?  I would
>   like root to have /bin/ksh.  I have to cludge it up with leaving the
>   default shell blank in /etc/passwd and then in the .profile put a:
>
>   exec /bin/ksh
>
>   This is annoying.

I don't know why it's done that  way, but it  looks like the check for
/bin/sh is coded into /bin/su.  (From a look at the binary.)

Another ploy for getting  ksh for root  is to simply  link /bin/ksh on
top of /bin/sh.  I've been running this way for quite a while  with no
problems (3.5).  I  do recall  some ancient problems with cron scripts
breaking and  log  files  growing forever  in the   2.5/3.0 days,  but
something fixed that.

	Bill Carpenter
	(AT&T gateways)!ho5cad!wjc
	HO 1L-410, (201)949-8392