From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: logrotate
Date: Wed, 01 Apr 2015 18:08:13 +0200 [thread overview]
Message-ID: <1427904493.3063.43.camel@ipfire.org> (raw)
In-Reply-To: <551C14FE.6010900@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2222 bytes --]
I am not aware that logrotate is not working.
https://bugzilla.ipfire.org/show_bug.cgi?id=10625 has been fixed with
one of the last Core Updates.
Best,
-Michael
On Wed, 2015-04-01 at 17:55 +0200, 5p9 wrote:
> Hi,
>
> i have the same problem with Core87 cleaninstall.
>
> I have do this workaround:
>
>
> > mkdir /etc/logrotate.d
>
> and then
>
> > logrotate -fv /etc/logrotate.conf
>
> then have no more problems with logrotate on this System.
>
> There is a problem since Core84 - here my forumpost (in german)
>
> https://forum.ipfire.org/viewtopic.php?f=6&t=11933&p=78727&hilit=logrotate#p77197
>
>
> 5p9
>
> Am 31.03.2015 um 09:10 schrieb Olaf Albrecht:
> > It seams that also the guardian.log will not rotate.
> >
> >
> >
> >
> >
> > Gesendet: Donnerstag, 5. März 2015 15:30
> > An: development(a)lists.ipfire.org
> > Betreff: logrotate
> >
> >
> >
> > Is it true that IPFire has a small logrotate bug? I have seen that my /var/log/messages has a size of 1,3 GB. When I start logrotate manually it says that the /etc/logrotate.d is missing. After creating that folder logrotate is starting without problems.
> >
> >
> >
> > Maybe I deleted that folder but I don't think so.
> >
> >
> >
> > Olaf
> >
> >
> >
> > Ferdinand Lusch GmbH & Co. KG
> > Im Brocke 11
> > 33649 Bielefeld
> > Tel: +49 (521) 9417 0
> > Fax: +49 (521) 9417 228
> > info(a)lusch.de
> > www.lusch.de
> >
> > Zweigwerk Buke:
> > Industriestrasse 21
> > 33184 Altenbeken-Buke
> > Tel: +49 (5255) 98890 0
> > Fax: +49 (5255) 98890 50
> >
> > Kommanditgesellschaft, Sitz u. Reg.-Ger. Bielefeld HRA 10273
> > Komplementaer: LUBRA Verwaltungsgesellschaft mbH,
> > Sitz u. Reg.-Ger. Bielefeld HRB 30 488
> > Geschaeftsfuehrer: Katharina Lusch, Wolfgang Exner
> >
> >
> >
> >
> >
> > _______________________________________________
> > Development mailing list
> > Development(a)lists.ipfire.org
> > http://lists.ipfire.org/mailman/listinfo/development
> >
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-01 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <002401d06b81$c325c510$49714f30$@lusch.de>
2015-04-01 15:55 ` logrotate 5p9
2015-04-01 16:08 ` Michael Tremer [this message]
2015-04-01 16:39 ` logrotate 5p9
[not found] <005101d05750$cba25cc0$62e71640$@lusch.de>
2015-03-05 14:49 ` logrotate Michael Tremer
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=1427904493.3063.43.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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