Am Freitag, 6. September 2002, 07:43:09 Uhr MET, schrieb David Walser:
My messages file is *huge* (because of the screwed up
autofs...) and there is no messages.1 or anything else.
I had once a broken entry in /etc/logrotate.d that stopped logrotate
from working. Try to execute
root@cooker# rpm -q logrotate
logrotate-3.6-1mdk
error: /etc/logrotate.conf:9 unexpected text
error running postrotate script
run-parts: /etc/cron.daily/logrotate exited with return code 1
/etc/logrotate.conf:
# see man logrotate for details
# rotate log files weekly
weekly
# keep 4 weeks
Oden Eriksson [EMAIL PROTECTED] writes:
I wonder if it would be possible to make a new logrotate package update that
only patches the /etc/logrotate.conf file like this:
done.
--
http://www.linux-mandrake.com/en/club/
On Mondayen den 31 December 2001 11.11, Chmouel Boudjnah wrote:
Oden Eriksson [EMAIL PROTECTED] writes:
I wonder if it would be possible to make a new logrotate package update
that only patches the /etc/logrotate.conf file like this:
done.
Cool!
giggle.
--
On Saturdayen den 29 December 2001 20.12, Neuromancer wrote:
Anyone know why I get the error:
error: /etc/logrotate.conf:9 unexpected text
whenever logrotate runs?
I actually commented out line 9 which is:
errors root
so that it will run.
Why doesn't logrotate accept this option?
-Russ
Because it does not support it. Check man logrotate.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Neuromancer
Sent: Saturday, December 29, 2001 2:13 PM
To: [EMAIL PROTECTED]
Subject: [Cooker] logrotate problems
Anyone know why I get
]
Subject: [Cooker] logrotate problems
Anyone know why I get the error:
error: /etc/logrotate.conf:9 unexpected text
whenever logrotate runs?
I actually commented out line 9 which is:
errors root
so that it will run.
Why doesn't logrotate accept this option?
I wonder if it would
I upgraded to the latest logrotate, but the logrotate.conf contained
therein seems to have a problem:
error: /etc/logrotate.conf:9 unexpected text
The line in quetion is:
errors root
Looking through the new manpage for logrotate, it does appear that
errors is no longer a recognised keyword.
On Saturdayen den 1 December 2001 18.18, Ryan T. Sammartino wrote:
I upgraded to the latest logrotate, but the logrotate.conf contained
therein seems to have a problem:
error: /etc/logrotate.conf:9 unexpected text
The line in quetion is:
errors root
Looking through the new manpage for
This was a bug in the logrotate config from 7.1, and should not be present
in a 7.2 install. (I just upgraded most of my packages to 7.2 level last
night). Also the config file in question is part of the sysklogd package.
--
Anton GrahamGPG ID: 0x18F78541
[EMAIL
On Tue, Nov 07, 2000 at 02:18:15PM +0100, Thierry SAURA wrote:
I have a problem with lograte and two rules :
/var/log/mail/* {
rotate 5
weekly
postrotate
/usr/bin/killall -HUP syslogd
endscript
}
/var/log/news/* {
rotate 5
Thierry SAURA a écrit :
I have a problem with lograte and two rules :
/var/log/mail/* {
rotate 5
weekly
postrotate
/usr/bin/killall -HUP syslogd
endscript
}
/var/log/news/* {
rotate 5
weekly
postrotate
So sprach Thomas Poindessous am Tue, Nov 07, 2000 at 03:16:31PM +0100:
For deleting them, try
for in in *.gz ; do rm -f $i; done
I don't understand, why does everyone want to delete each file seperately?
a ls -lad /var/log/{mail,news} to find out the permissions and rm -rfv
I have a problem with lograte and two rules :
/var/log/mail/* {
rotate 5
weekly
postrotate
/usr/bin/killall -HUP syslogd
endscript
}
/var/log/news/* {
rotate 5
weekly
postrotate
/usr/bin/killall -HUP syslogd
On Tue, Nov 07, 2000 at 03:23:19PM +0100, Frederic Crozat wrote:
somebody has an idea about where the problem comes from ? bad rules ?
logrotate bug ?
It's a logrotate bug and Renaud (sysklog maintainer) has modified
logrotate config file to circonvent this bug ..
You have probably
Christian Gennerat wrote:
Thierry SAURA a écrit :
I have a problem with lograte and two rules :
/var/log/mail/* {
rotate 5
weekly
postrotate
/usr/bin/killall -HUP syslogd
endscript
}
/var/log/news/* {
rotate 5
It should be fixed in the last release of sysklogd package,
by replacing all global * (as in /var/log/daemons/*) in the
syslog conf file placed in /etc/logrotate.d by explicit
base names of log files.
A patch had been applied to prevent logrotate from rotating
compressed archives but that
logrotate stills runs "forever". something is
very wrong.
This was a known issue solved a while ago. The
problem lies in two sections of
/etc/logrotate.d/syslog beginning with:
/var/log/mail/*
and
/var/log/news/*
These lines rotate all the files in those
directories, including the files
logrotate 3.3-8mdk (and 6mdk for that matter), run forever and never
end. I have this set up as part of my /etc/cron.dailyRunning it
with "-d" I get the "reading" the various configs and lots of disk I/O.
logrotate is taking 94% of the CPU and 20% of memory. I had not noticed
this
I am deleting /var/log/news as I type this. It is taking a while. I
don't even run a news server and can't recall when I last looked in this
directory.
thx for the idea I'll see it this clears things up
jim drash
[EMAIL PROTECTED]
Stefan van der Eijk wrote:
logrotate 3.3-8mdk (and 6mdk
logrotate stills runs "forever". something is very wrong.
jdrash wrote:
I am deleting /var/log/news as I type this. It is taking a while. I
don't even run a news server and can't recall when I last looked in this
directory.
thx for the idea I'll see it this clears things up
jim
This simply isn't playing nice :/ On its daily run, it's fine, but on
the weekly, it runs for well over an hour restarting syslogd several
times per second. It hasn't completed yet for this weekly rotate, but:
root@bladehawke /var/log # head syslog; echo ; tail syslog; echo ; \
grep "syslogd
Submitted 20-Aug-00 by myself:
No matter what kind of rotation is needed, restarting syslogd 13,478
times is a _little_ overboard. If last week's logs are any indication,
I'm about 2/3 of the way through it:
This week's (i.e. today's) tally was 42,988 restarts ending at 17:16:05.
--
Anton
I reported this the other day with the subject
infinite logs. The culprit are the entries for mail
and news in the "/etc/logrotate.d/syslog":
/var/log/mail/* {
rotate 5
weekly
postrotate
/usr/bin/killall -HUP syslogd
endscript
}
/var/log/news/* {
Submitted 21-Aug-00 by Eugenio Diaz:
The problem is that using an "*" alone would cause
**all** files in the dir to be rotated, including the
previosly rotated files, and as a result you will get
more and more files with longer and longer filenames
each day.
That would definitely appear to
It seems to be worng path to killall in /etc/logrotate.d/syslog
It tries to run /sbin/killall -HUP syslogd, but the only killall I have is
in /usr/bin
/M
26 matches
Mail list logo
