From owner-freebsd-questions Sun May 10 12:02:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23613 for freebsd-questions-outgoing; Sun, 10 May 1998 12:02:33 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23603 for ; Sun, 10 May 1998 12:02:26 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id MAA25244; Sun, 10 May 1998 12:02:21 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Sun, 10 May 1998 12:02:20 -0700 (PDT) From: Doug White Reply-To: Doug White To: Shawn Ramsey cc: questions@FreeBSD.ORG Subject: Re: Cron In-Reply-To: <19980509154503.04058@cpl.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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