From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] logrotate won't rotate portage logs
Date: Mon, 15 Jan 2007 19:32:46 +0000 [thread overview]
Message-ID: <358eca8f0701151132v6ef24209paa43700aa6d47f8f@mail.gmail.com> (raw)
Hi All,
I do not understand why the log files within /var/log/portage/ will
not rotate on my PC, while they rotate fine on my laptop. The
/etc/logrotate.conf is the same on both boxen:
==========================================
# rotate log files weekly
weekly
#daily
# keep 4 weeks worth of backlogs
rotate 4
# create new (empty) log files after rotating old ones
create
# uncomment this if you want your log files compressed
compress
# packages can drop log rotation information into this directory
include /etc/logrotate.d
notifempty
nomail
noolddir
[snip . . . ]
# when /var/log/portage gets big
/var/log/portage/*.log
{
rotate 1
weekly
nocreate
ifempty
olddir /var/log/portage/old
postrotate
find /var/log/portage/old -maxdepth 1 -mtime +30 -exec /bin/rm -f {} \;
endscript
nocompress
}
==========================================
The only difference I noticed (other than the fact that I have two
year old portage log files in /var/log/portage) between the two boxen
is that the access rights of the 'old' directory on the PC were:
drwxr-sr-x 2 root root 48 Dec 23 2005 old
while on the laptop which rotates without problems are:
drwx------ 2 root root 4256 Jan 13 11:20 old
This may be a bit of a red herring because even though I changed the
access rights as per the laptop, the PC still refuses to rotate the
portage log files.
Any ideas? How do I troubleshoot this one?
--
Regards,
Mick
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2007-01-15 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 19:32 Mick [this message]
2007-01-20 0:34 ` [gentoo-user] Re: logrotate won't rotate portage logs Mick
2007-01-20 15:24 ` Hans-Werner Hilse
2007-01-20 16:46 ` Mick
2007-01-21 14:21 ` Hans-Werner Hilse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=358eca8f0701151132v6ef24209paa43700aa6d47f8f@mail.gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox