Project

General

Profile

Actions

Bug #4551

closed

Initial logrotate configuration (from initial-promises) does not include recent fixes

Added by Jonathan CLARKE over 10 years ago. Updated over 10 years ago.

Status:
Released
Priority:
2
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

The logrotate configuration files should be the same in initial promises and techniques. However, currently there are several differences.

This is really a low impact bug, since the initial promises don't get used for very long at all on a policy server, since a promise generation is almost the first thing that happens. However, this can cause unrequired repairs, and possibly variations in behaviour that could be confusing to debug.


Subtasks 2 (0 open2 closed)

Bug #4554: Initial logrotate configuration (from initial-promises) does not apply delaycompress optionReleasedJonathan CLARKE2014-03-05Actions
Bug #4556: Log file about non compliant reports is not managed by logrotate on Red Hat-like Rudder serverReleasedMatthieu CERDA2014-03-05Actions

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #4445: Wrong permissions slapd.log after logrotateReleasedJonathan CLARKE2014-02-06Actions
Actions

Also available in: Atom PDF