Project

General

Profile

Actions
Copy link

Bug #6842

closed

Edit only one syslog configuration at a time

Added by Matthieu CERDA almost 9 years ago. Updated almost 9 years ago.

Status:
Rejected
Priority:
1
Assignee:
Benoît PECCATTE
Category:
System integration
Target version:
2.10.15
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

We currently edit all the syslogs config we can detect.

This is stupid, as in the large majority of the cases there can be only one active syslog service...

We should just edit the first syslog we detect and pass on, in the order:
  • rsyslog (majority of recent OSes)
  • syslog-ng (especially SLES10, used on some setups too)
  • syslogd (highly deprecated, used by RHEL5 and AIX)
Actions
Copy link
 #1

Updated by Matthieu CERDA almost 9 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Matthieu CERDA to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/705
Actions
Copy link
 #2

Updated by Benoît PECCATTE almost 9 years ago

  • Status changed from Pending technical review to Rejected

I prefer having to edit 2 files while we need to edit only one, to editing the wrong file and break the reporting.

Actions
Copy link

Also available in: Atom PDF