Hi My /var/log/messages is growing, is there a standard way to rotate this? The same goes for zypper.log which used to rotate, the last time it was 04-Nov last year. I'm sure this was al automatic at one point in time. regards Ian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
ianseeks wrote:
Hi
My /var/log/messages is growing, is there a standard way to rotate this? The same goes for zypper.log which used to rotate, the last time it was 04-Nov last year. I'm sure this was al automatic at one point in time.
logrotate is the standard way to do it. In 13.2 it's driven by a systemd timer, but it's not been enabled by default. See "systemctl status logrotate.timer". -- Per Jessen, Zürich (5.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday 13 Mar 2015 13:44:51 Per Jessen wrote:
ianseeks wrote:
Hi
My /var/log/messages is growing, is there a standard way to rotate this? The same goes for zypper.log which used to rotate, the last time it was 04-Nov last year. I'm sure this was al automatic at one point in time.
logrotate is the standard way to do it. In 13.2 it's driven by a systemd timer, but it's not been enabled by default. See "systemctl status logrotate.timer". Thanks Per. It was Inactive(dead), surprised its not enabled by default. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/13/2015 09:10 AM, ianseeks wrote:
On Friday 13 Mar 2015 13:44:51 Per Jessen wrote:
ianseeks wrote:
Hi
My /var/log/messages is growing, is there a standard way to rotate this? The same goes for zypper.log which used to rotate, the last time it was 04-Nov last year. I'm sure this was al automatic at one point in time.
logrotate is the standard way to do it. In 13.2 it's driven by a systemd timer, but it's not been enabled by default. See "systemctl status logrotate.timer". Thanks Per. It was Inactive(dead), surprised its not enabled by default.
I've been delaying upgrading from 13.1 to 13.2 I always delay upgrades. The day 1 release on the DVD always has some problems/bugs/hazards. I get the feeling that 13.2 has more than 13.1 did, but that may simply be an observer fallacy. I know that the DVD doesn't get updated and the updates from the repositories will address many issues. The longer I wait the greater the flood of initial updates will be. But I wonder if things like this will be in that flood? while trivial to correct this is a non-trivial shortcoming. As Ian points out, the log files will just grown and grow unless logrotate is run, and 'out of the box' its not going to run. I realise that many updates in the update repository will only come about as a result of bug reports - if then! If at all! This might not be considered a real bug. I'm just wondering about many "if"s in all this. How much will get fixed in repo-update and how much is a matter of combing this list and applying fixes like this one manually? part of the reason I ask is that this is a baseline system item, not the kind of thing that is an if-but-may-be-only-some-users type, hardware dependent or something. Its a basic function and it not working is a serious deficiency compared to the baseline of previous releases. This isn't purely a systemd conversion matter. As Per points out, its there, its just not enabled by default 'out of the box'. Its a configuration issue. The system packagers should have enabled it. So: how much is foxed in repo-update and how much do we have to do manually? What about openSuse users who don't subscribe to this list? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 13/03/15 14:36, Anton Aylward wrote:
On 03/13/2015 09:10 AM, ianseeks wrote:
On Friday 13 Mar 2015 13:44:51 Per Jessen wrote:
ianseeks wrote:
Hi
My /var/log/messages is growing, is there a standard way to rotate this? The same goes for zypper.log which used to rotate, the last time it was 04-Nov last year. I'm sure this was al automatic at one point in time.
logrotate is the standard way to do it. In 13.2 it's driven by a systemd timer, but it's not been enabled by default. See "systemctl status logrotate.timer". Thanks Per. It was Inactive(dead), surprised its not enabled by default.
I've been delaying upgrading from 13.1 to 13.2 I always delay upgrades. The day 1 release on the DVD always has some problems/bugs/hazards. I get the feeling that 13.2 has more than 13.1 did, but that may simply be an observer fallacy. I know that the DVD doesn't get updated and the updates from the repositories will address many issues. The longer I wait the greater the flood of initial updates will be.
But I wonder if things like this will be in that flood? while trivial to correct this is a non-trivial shortcoming. As Ian points out, the log files will just grown and grow unless logrotate is run, and 'out of the box' its not going to run.
I realise that many updates in the update repository will only come about as a result of bug reports - if then! If at all! This might not be considered a real bug.
I'm just wondering about many "if"s in all this. How much will get fixed in repo-update and how much is a matter of combing this list and applying fixes like this one manually?
part of the reason I ask is that this is a baseline system item, not the kind of thing that is an if-but-may-be-only-some-users type, hardware dependent or something. Its a basic function and it not working is a serious deficiency compared to the baseline of previous releases.
This isn't purely a systemd conversion matter. As Per points out, its there, its just not enabled by default 'out of the box'. Its a configuration issue. The system packagers should have enabled it.
So: how much is foxed in repo-update and how much do we have to do manually? What about openSuse users who don't subscribe to this list?
That's exactly my own feelings and why I'm holding off on 13.2 for the meantime, bar one machine where I have it installed temporarily to be able to do one task. The (non)-cleaning of temp directories is another of those obscurely-documented defaults that requires manual intervention. If these things really are intentional then I think they at least merit a mention in the Release Notes. Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 03/13/2015 09:10 AM, ianseeks wrote:
On Friday 13 Mar 2015 13:44:51 Per Jessen wrote:
ianseeks wrote:
Hi
My /var/log/messages is growing, is there a standard way to rotate this? The same goes for zypper.log which used to rotate, the last time it was 04-Nov last year. I'm sure this was al automatic at one point in time.
logrotate is the standard way to do it. In 13.2 it's driven by a systemd timer, but it's not been enabled by default. See "systemctl status logrotate.timer". Thanks Per. It was Inactive(dead), surprised its not enabled by default.
I've been delaying upgrading from 13.1 to 13.2 I always delay upgrades. The day 1 release on the DVD always has some problems/bugs/hazards. I get the feeling that 13.2 has more than 13.1 did, but that may simply be an observer fallacy. I know that the DVD doesn't get updated and the updates from the repositories will address many issues. The longer I wait the greater the flood of initial updates will be.
But I wonder if things like this will be in that flood?
Unless somebody reports the problem, it most likely wont. I haven't reported it because I have my own logrotate setup, which is run via cron. -- Per Jessen, Zürich (5.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Anton Aylward -
ianseeks -
Per Jessen -
Peter