From owner-freebsd-current Mon Mar 31 19:38:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA04848 for current-outgoing; Mon, 31 Mar 1997 19:38:43 -0800 (PST) Received: from veda.is (ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA04842 for ; Mon, 31 Mar 1997 19:38:39 -0800 (PST) Received: (from adam@localhost) by veda.is (8.8.4/8.7.3) id EAA28007; Tue, 1 Apr 1997 04:00:31 GMT Date: Tue, 1 Apr 1997 04:00:31 GMT From: Adam David Message-Id: <199704010400.EAA28007@veda.is> To: jdp@polstra.COM (John Polstra) Cc: freebsd-current@freebsd.org Subject: Re: sendmail and 2.2.1R not happy Newsgroups: list.freebsd.current References: <199703302103.OAA01705@Ilsa.StevesCafe.com> <199703311630.IAA09912@austin.polstra.com> X-Newsreader: NN version 6.5.0 #2 (NOV) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >In article <199703302103.OAA01705@Ilsa.StevesCafe.com>, >Steve Passe wrote: >> Mar 29 19:19:39 Sam sendmail[540]: /etc/pwd.db: Permission denied >> Mar 29 19:19:39 Sam sendmail[540]: LAA04887: SYSERR(UID1): Cannot exec >> /usr/libexec/mail.local: Permission denied I've seen stuff like this quite often after updating binaries in a running system. Come to think of it, I've also seen this kind of stuff spontaneously after fairly long uptimes, and with no obvious triggering condition. Once in a while no exec's are possible (permission denied, segmentation violation, bus error, whatever). Then after awhile it tends to clear up by itself. This is with NFS mounted /usr. BTW, have the recently introduced NFS exec panics been taken care of yet and fixed? -- Adam David