Xref: utzoo comp.unix.misc:328 comp.unix.xenix.sco:474 comp.unix.internals:665 comp.unix.sysv386:1226 comp.unix.shell:581
Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!ncoast!fmsystm!bmhalh!ACT!bruce
From: bruce@ACT.UUCP (Bruce Himebaugh)
Newsgroups: comp.unix.misc,comp.unix.xenix.sco,comp.unix.internals,comp.unix.sysv386,comp.unix.shell
Subject: Summary of why csh doesn't work for root login
Keywords: summary csh sh root login
Message-ID: <10@ACT.UUCP>
Date: 11 Oct 90 21:04:39 GMT
Lines: 32

A while ago I posted an article asking people for help on why csh would not
work as the shell for the root login.  This article simply summarizes the
responses I got.

The original article I posted was something to this effect:

    At work we have a 386 system (used for accounting) running SCO Unix.  I
    changed the shell for root (in the /etc/passwd file), from '/bin/sh' to
    '/bin/csh'.  Boy did this cause problems.  Everything works fine, until you
    reboot the system.  While the system is coming up (e.g. starting cron,
    print services, etc.) it starts displaying the /etc/motd (i.e. message of
    the day) file.  It also trashes the /etc/mnttab file and /etc/systemid
    file.

Summary of responses:

    1.  It is a documented bug in SCO Unix Version 0.  It is suppose to be
	fixed in a future release.

    2.  A couple people suggested making two root logins, like:

	    root:*:0:0:Superuser:/:/bin/sh
	    cshroot:*:0:0:Superuser:/:/bin/csh

That really sums it up.  Thank you for all the responses.

Bruce
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Bruce Himebaugh             A.C.T. Consulting, Inc.         Voice: 216-455-1444
   PATHS: uunet!{ncoast,aablue}!fmsystm!mrsmouse!bmhalh!ACT!bruce
          (NOTE: the system name "fmsystm" is with no "e", NOT "fmsystem")
  *NOTE*: Please do not use bruce@ACT.UUCP -- I'm not registered yet.