Project

General

Profile

Actions
Copy link

Bug #14928

closed

Syslog service to use priority is wrong

Added by Alexis Mousset almost 5 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
Alexis Mousset
Category:
System techniques
Target version:
5.0.15
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

Currently syslog has precedence over rsyslog, this makes no sense. A leftover syslog.conf prevents Rudder from working correctly.

Actions
Copy link
 #1

Updated by Alexis Mousset almost 5 years ago

  • Status changed from New to In progress
  • Assignee set to Alexis Mousset
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.12 to 5.0.13
Actions
Copy link
 #3

Updated by Alexis Mousset almost 5 years ago

  • Category set to System techniques
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.14 to 5.0.15
Actions
Copy link
 #6

Updated by Alexis Mousset over 4 years ago

  • Status changed from In progress to Rejected

We probably won't change this as syslog reporting is being replaced, and we won't change this is minor releases. Closing.

Actions
Copy link

Also available in: Atom PDF