Date: Thu, 10 Oct 2002 11:37:08 +0100 From: "Jamie Heckford" <jamie@jamiesdomain.org.uk> To: "Maxim Konovalov" <maxim@FreeBSD.org> Cc: "Naga Suresh B" <torvalds@addr.com>, <freebsd-stable@FreeBSD.org> Subject: Re: disk running out of space Message-ID: <008901c27048$fc1bc5f0$3264a8c0@BONG> References: <01a201c27042$51fe54d0$9600a8c0@blraddrcom> <20021010135051.Q16902-100000@news1.macomnet.ru> <01e401c27044$67b8da50$9600a8c0@blraddrcom> <007301c27045$9b32fea0$3264a8c0@BONG> <20021010141810.X22800-100000@news1.macomnet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Ahhh. I love picking up the simple things after I've been using FreeBSD for about 4 years :P ----- Original Message ----- From: "Maxim Konovalov" <maxim@FreeBSD.org> To: "Jamie Heckford" <jamie@jamiesdomain.org.uk> Cc: "Naga Suresh B" <torvalds@addr.com>; <freebsd-stable@FreeBSD.org> Sent: Thursday, October 10, 2002 11:21 AM Subject: Re: disk running out of space > > http://www.freebsd.org/doc/faq/disks.html#DU-VS-DF > > "When a program is using a file, and you delete the file, the file is > not really removed from the filesystem until the program stops using > it." > > SIGHUP tells syslogd to reopen logfiles, apachectl restart does the > same for apache. > > It's really belongs to -questions. > > On 14:12+0400, Oct 10, 2002, Jamie Heckford wrote: > > > hmmmm - could possibly be your log files if there going into /var > > ..... could only be explained if apache is cleaning the logs on a > > restart somehow. > > > > btw, why would sending syslogd a SIGHUP help just out or curiosity? > > > > ----- Original Message ----- > > From: "Naga Suresh B" <torvalds@addr.com> > > To: "Maxim Konovalov" <maxim@FreeBSD.ORG> > > Cc: <freebsd-current@FreeBSD.ORG>; <freebsd-stable@FreeBSD.ORG> > > Sent: Thursday, October 10, 2002 11:04 AM > > Subject: Re: disk running out of space > > > > > > > Thank you for your suggestion I restarted apache on my server my df -h is > > > giving > > > > > > Filesystem Size Used Avail Capacity Mounted on > > > /dev/ad0s2a 9.6G 1.0G 7.8G 12% / > > > /dev/ad2s1e 55G 39G 11G 77% /data > > > /dev/ad0s1e 9.6G 2.0K 8.8G 0% /data2 > > > /dev/ad0s3e 26G 1.0G 23G 4% /data3 > > > /dev/ad0s2e 9.6G 1.9G 6.9G 22% /usr > > > procfs 4.0K 4.0K 0B 100% /proc > > > > > > What might be the problem??? In future how can I overcome this type of > > > problems without restarting the service. > > > > > > Suresh > [...] > > -- > Maxim Konovalov, maxim@FreeBSD.org > > > -- ____________________________________________________ Message scanned for viruses and dangerous content by <http://www.newnet.co.uk/av/>; and believed to be clean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?008901c27048$fc1bc5f0$3264a8c0>