Date: Sun, 10 May 1998 12:02:20 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: Shawn Ramsey <shawn@cpl.net> Cc: questions@FreeBSD.ORG Subject: Re: Cron Message-ID: <Pine.BSF.3.96.980510120014.4464H-100000@gdi.uoregon.edu> In-Reply-To: <19980509154503.04058@cpl.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 9 May 1998, Shawn Ramsey wrote:
> > > in order to fix this i just need to change the roots shell to sh???
> >
> > Yes. You should never change root's shell, no matter how tempting.
>
> What are the consquences of changed root's shell?? I've changed root shell,
> and havent noticed any problems...
1) Unintended changes to scripts run as root.
2) Shared-lib issues -- pick the wrong shell and you won't be able to
login as root if, say, /usr or /lib dies and takes libc with it.
/bin/sh is statically linked.
3) Use su -m (to pick up the user's environment) or sudo instead (to
avoid the whole root shell problem altogether).
Doug White | University of Oregon
Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite | Computer Science Major
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980510120014.4464H-100000>