Date: Fri, 1 Feb 2002 16:38:59 -0800 From: "Crist J. Clark" <cristjc@earthlink.net> To: "Dennis I. Kovarsky" <dennis.kovarsky@usask.ca> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: df Message-ID: <20020201163859.A1280@gohan.cjclark.org> In-Reply-To: <Pine.OSF.4.31.0202011518360.69310-100000@duke.usask.ca>; from dennis.kovarsky@usask.ca on Fri, Feb 01, 2002 at 03:24:37PM -0600 References: <Pine.OSF.4.31.0202011518360.69310-100000@duke.usask.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 01, 2002 at 03:24:37PM -0600, Dennis I. Kovarsky wrote: > > FreeBSD-4.4R, a file in /var/log keeps filling up the FS. Newsyslog > solution has been implemented, however, the question remains. > > According to the Handbook article on "output from df vs. du", the cause > for the mismatch in the outputs is the fact that there's a process with > the lock on the file. > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#DU-VS-DF > > However, doing a kill -HUP on the offending daemon doesn't help. In fact, > HUPping each and every one of the entries in "ps -ax" doesn't work. > Rebooting seems to be the only solution at this point. Needless to say, > that is not a desirable solution. What a daemon does when it receives a SIGHUP is totally up to the daemon. It may or may not be closing open file descriptors to log files. Try terminating each process to see which one it might be. You can also look at fstat(1) output for suspects. Check if they have any open files in /var that you cannot find(1) by the inode number. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org 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?20020201163859.A1280>