Project

General

Profile

Actions
Copy link

Bug #5488

closed

Do not write into cf3.[hostname].runlog files used for debug or CFEngine Enterprise edition

Added by Lionel Le Folgoc about 10 years ago. Updated over 9 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Matthieu CERDA
Category:
System integration
Target version:
2.11.3
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Hi,

  1. du -sh /var/rudder/cfengine-community/
    606M /var/rudder/cfengine-community/
  2. du -sh /var/rudder/cfengine-community/cf3.myhost.runlog
    532M /var/rudder/cfengine-community/cf3.myhost.runlog

I have the (secret) wish to be able to use my systems for useful things, and adding a cronjob to clean *.runlog every minute/hour/day/week is not one of them.
Any chance they could be purged or rotated or something?

Thanks.

More information about these file can be found here: https://docs.cfengine.com/docs/3.6/guide-introduction-directory-structure.html#log-files-in-var-cfengine.

FAR note: as a workaround, you can either:
- create a symlink to /dev/null
- or create a cronjob that remove the file periodically (for ex: 0 0,12 * * * root rm -f /var/rudder/cfengine-community/*.runlog* )

Actions
Copy link

Also available in: Atom PDF