Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!lll-winken!cert!netnews.upenn.edu!scrolls.wharton.upenn.edu!catone
From: catone@scrolls.wharton.upenn.edu (Tony Catone)
Newsgroups: comp.unix.ultrix
Subject: Re: su bug in Ultrix 4.1 still there
Message-ID: <34747@netnews.upenn.edu>
Date: 13 Dec 90 20:49:21 GMT
References: <RUSTY.90Dec10144456@belch.Berkeley.EDU> <1990Dec11.045743.27648@decuac.dec.com> <1990Dec12.024324.13947@cerberus.bhpese.oz.au>
Sender: news@netnews.upenn.edu
Distribution: comp
Organization: desci
Lines: 18

In article <1990Dec12.024324.13947@cerberus.bhpese.oz.au> Sm@cerberus.bhpese.oz.au (Scott Merrilees) writes:
>It seems that your ideas and mine are totally opposed.  I think that
>log in as root should be avoided in just about all cases, and that the
>priviledged user should first log into their own account, then su to
>root where necessary. . .

This would be fine, except that the su command does not work properly
on all Unix implementations.  That is, command behavior is not identical
for root login and su'ing to root.  My most recent encounter with this
problem has been IBM AIX PS/2 1.1.  The same problem existed in IBM
AIX RT 2.2.1; behavior was even worse that PS/2 1.1.  I don't know how
Ultrix behaves on this scale, since we are just setting up our 5000/200's,
but in general I am wary of the su command for these reasons.  Root
logins always work; su may or may not; life is complicated enough without
these problems.

- Tony
  catone@desci.wharton.upenn.edu