Date: Sun, 10 Jun 2001 10:02:13 -0700 From: "Dave Atkins" <dave@atkinshome.com> To: <freebsd-questions@FreeBSD.ORG> Subject: small /var partition; how do I prevent log file overflow? Message-ID: <001001c0f1cf$18be68b0$0300a8c0@dave> In-Reply-To: <000701c0f077$1e6342d0$0300a8c0@dave>
next in thread | previous in thread | raw e-mail | index | archive | help
I've done this so many times now on various operating systems that I should know better...but when I did the install of freebsd 4, I let the install program set up my partitions. Now, I've got this great setup: FreeBSD 4.3-RELEASE (DAVE) #1: Sat Jun 9 15:52:40 PDT 2001 $ df -k Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 99183 35244 56005 39% / /dev/ad0s1f 1350983 614495 628410 49% /usr /dev/ad0s1e 19815 1264 16966 7% /var procfs 4 4 0 100% /proc My concern is that /var is so small. I am running a firewall and doing limited logging, but still, I can imagine 20 Meg of log files happening. I will never *need* 20 meg of logs, so how can I configure things to avoid overflowing space? As I recall, the log files somehow cycle/rotate (maillog does a daily file and compresses itself). I'm going to turn off sendmail anyway, so I won't worry about the spool directory, but I am nervous about /var/log/security and the other log files. I have seen several systems crash because of DoS attacks or just forgetfulness on the part of the sysadmin that led to exploding log files. What is the best way to cap these files and prevent the situation from getting out of control? Thanks 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?001001c0f1cf$18be68b0$0300a8c0>