Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: =?UTF-8?B?8J+HtfCfh7FKYWNlayBNYXJjaW4gSmF3b3Jza2nwn4e18J+HsQ==?= <jmj@energokod.gda.pl>
Newsgroups: comp.os.linux.misc
Subject: Re: ever had 1GB+ kern.log (and syslog) from changing monitors?
Date: Tue, 13 Jan 2026 08:09:56 +0100
Organization: energokod.gda.pl
Lines: 22
Message-ID: <msm9e4Fg2l4U6@mid.individual.net>
References: <slrn10mbk6i.uec.spamtrap42@one.localnet> <SOKcnS4SSfV1Rfj0nZ2dnZfqnPqdnZ2d@giganews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net /HOhnbZuKKCNrUvRKvAI/wF0Tdt5nNnVqw9wZWRmZJxWaNRgPY
Cancel-Lock: sha1:x704D50jzLEcbbpdIMPk/LKwTdk= sha256:piQg/Pbq2PNnz4Y664FmBWc1JDdcuW7fgisjtCILJ6c=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0
Content-Language: en-GB
In-Reply-To: <SOKcnS4SSfV1Rfj0nZ2dnZfqnPqdnZ2d@giganews.com>
Xref: csiph.com comp.os.linux.misc:81053

W dniu 13.01.2026 o 06:32, c186282 pisze:
>    You can either do a LOT of research OR just write
>    a root crontab script that nukes "older" logs.

There are better options:
1. Separate /var partition, and
2. Setup logrotate: <https://linux.die.net/man/8/logrotate>

Then logs will newer exceed /var partition size limit, and in the case 
of flood logs rest of OS will be not affected.

Logrotate should automatically delete older logs. Even in the case of 
flood logs.

-- 
Jacek Marcin Jaworski,    Pruszcz Gd., woj. Pomorskie, Polska🇵🇱, EU🇪🇺;
tel.: +48-609-170-742,   najlepiej w godz.: 5:15-5:55 lub 17:15-17:55;
<jmj@energokod.gda.pl>, gpg: 4A541AA7A6E872318B85D7F6A651CC39244B0BFA;
Domowa s. WWW:                             <https://energokod.gda.pl>;
Mini Netykieta:         <https://energokod.gda.pl/MiniNetykieta.html>;
Mailowa Samoobrona:             <https://emailselfdefense.fsf.org/pl>.