Date: 6 Dec 2002 16:30:04 -0000 From: gary@outloud.org To: FreeBSD-gnats-submit@FreeBSD.org Subject: misc/46409: Certain periodic scripts check broken NFS mounts. Message-ID: <20021206163004.56065.qmail@bsd.webjockey.net>
next in thread | raw e-mail | index | archive | help
>Number: 46409 >Category: misc >Synopsis: Certain periodic scripts check broken NFS mounts. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Dec 20 13:00:06 PST 2002 >Closed-Date: >Last-Modified: >Originator: >Release: FreeBSD 5.0-CURRENT i386 >Organization: >Environment: System: FreeBSD napalm.outloud.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Sep 2 06:16:55 EDT 2002 root@napalm.outloud.org:/usr/src/sys/i386/compile/Ancient.Kernel i386 >Description: Some of the scripts located in periodic/security (and others?) usually check all the mount points for suid files. However, under certain conditions, such as dead NFS (over TCP) mounts can cause the find(1) to hang and become a problem. >How-To-Repeat: Setup an enviorment where a remote NFS mount over TCP, become "dead". Then run periodic/security/100.chksetuid, and find(1) will hang in memory. I cannot seem to kill the find process, and a reboot is the only thing that fixes this. >Fix: Patching some of the find scripts within periodic/ to only do local mounts and not NFS ones seems to be a fix, and using NFS over UDP is another option. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021206163004.56065.qmail>