Actions
Bug #13993
closedUse of syslog results in all log messages at priority "emerg"
% Done:
0%
Source:
Development
Tags:
Backport:
infernalis,hammer
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
In src/log/Log.cc we call syslog like so;
syslog(LOG_USER, "%s%s", buf, s.c_str());
syslog(LOG_USER, "%s", s);
Calling syslog with LOG_USER alone implies LOG_USER|LOG_EMERG and causes the messages to be logged at emergency priority.
Updated by Kefu Chai over 8 years ago
- Status changed from New to Fix Under Review
- Source changed from other to Development
Updated by Nathan Cutler over 8 years ago
jewel PR: https://github.com/ceph/ceph/pull/6815
Updated by Sage Weil over 8 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Brad Hubbard over 8 years ago
- Copied to Backport #14137: infernalis: Use of syslog results in all log messages at priority "emerg" added
Updated by Brad Hubbard over 8 years ago
- Copied to Backport #14138: hammer: Use of syslog results in all log messages at priority "emerg" added
Updated by Brad Hubbard about 8 years ago
- Status changed from Pending Backport to Resolved
Updated by Brad Hubbard almost 8 years ago
- Related to Bug #15808: Assign LOG_INFO priority to syslog calls added
Actions