From owner-freebsd-stable Fri Jul 5 4:22:23 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CFB137B400 for ; Fri, 5 Jul 2002 04:22:21 -0700 (PDT) Received: from serv1-mk3.ilse.net (serv1-mk3.ilse.nl [62.69.160.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A9AB43E3B for ; Fri, 5 Jul 2002 04:22:15 -0700 (PDT) (envelope-from marcolz@serv1-mk3.ilse.net) Received: (from marcolz@localhost) by serv1-mk3.ilse.net (8.12.3/8.12.3) id g65BMBUr020083; Fri, 5 Jul 2002 13:22:11 +0200 (CEST) (envelope-from marcolz) Date: Fri, 5 Jul 2002 13:22:10 +0200 From: Marc Olzheim To: stable@FreeBSD.ORG Cc: marcolz@stack.nl Subject: /bin/sh, $MAIL and login.conf Message-ID: <20020705132210.A20062@ilse.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi. I was wondering why /etc/login.conf makes the login shell for root check for mail in /var/mail/root. Most systems I use have /var/mail nfs-mounted from a central mailserver. When there are networking problems and thus all operations on /var/mail keep 'hanging', I would like to be able to login as root on console and fix it. With the default login.conf, this is not possible though, since one of the first things /bin/sh does, is check $MAIL for new mail. So I have three questions: 1) Am I the only one with this kind of problem ? 2) Is there (going to be) an 'unsetenv' possibility in login.conf, so that I can still use 'default' for all classes and just unsetenv MAIL for sysadmins and root ? 3) Why does /bin/sh in non-interactive mode _also_ check $MAIL ? If an NFS mounted filesystem is non-responsive, all crons that use /bin/sh will keep hangig until the filesystem responds. If the problem remains long enough, the machine will simply run out of memory and/or processes because of all the hanging /bin/sh's... Does anybody have a good reason why it should behave like this ? Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message