Bug #7457
closed
User story #7361: Add an option to disable reporting globally
User story #7441: Remove syslog reporting when reports are disabled
restart syslog after deleting rudder-agent.conf in report disabled mode
Added by Vincent MEMBRÉ almost 9 years ago.
Updated almost 9 years ago.
Category:
System techniques
Description
syslog is still sending messages after reporting is disabled since syslog services are not restarted after confile is deleted/modified
- Tracker changed from User story to Bug
- Status changed from New to In progress
- Assignee set to Jonathan CLARKE
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/782
- Status changed from Pending technical review to In progress
- Assignee changed from Benoît PECCATTE to Jonathan CLARKE
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.2.0~beta1 which was released today.
- Related to Bug #12139: If we a have generic method command_execution with parameter /bin/true, we get an error on reporting for syslog restart on non-aix nor solaris sytem added
Also available in: Atom
PDF
Updated by 
Updated by Jonathan CLARKE 
Updated by 
Updated by