hi all
the var partition on my apache box may be too small.
this is a problem because -
i originally had newsyslog set at
/var/log/httpd-access.log 644 7 100 24B /var/run/httpd.pid 30
which sets httpd-access.log to be rotated in binary format everytime it reaches 100 mb
Redmond Militante wrote:
hi all
the var partition on my apache box may be too small.
this is a problem because -
i originally had newsyslog set at
/var/log/httpd-access.log 644 7 100 24B /var/run/httpd.pid 30
which sets httpd-access.log to be rotated in binary format
hi
a cron job that moves httpd-access.logs to an archive directory sounds like a fine
idea - is it safe, though to move these logs while apache and syslogd are running? or
would the cron job need to stop those apps first, move the logs, then restart
apache/syslogd?
thanks
redmond
[Fri, Oct
hello
i have a practice box set up, i've been trying to resizing /var by symlinking it to
/usr/var
in theory this is simple - my methodology is
drop to single user mode
fsck -p
mount -u /
mount -a -t ufs
swapon -a
adjkerntz -i
mkdir /usr/var
cd /var
cp -R * /usr/var
cd ../
mv /var /var-old
ln
[ sorry about not quoting - braindead mail client ]
Moving a filesystem on a live server is *never* a risk-free activity. If
you intend to do this, use tar(1) or dump(8) instead of cp(1) - they
will deal with special files and other unusual conditions.
But if you haven't done this often enough
On Fri, Oct 03, 2003 at 09:00:43AM -0500, Redmond Militante wrote:
hi all
the var partition on my apache box may be too small.
this is a problem because -
i originally had newsyslog set at
/var/log/httpd-access.log 644 7 100 24B /var/run/httpd.pid 30
fwiw I have