Skip to content
Snippets Groups Projects
Select Git revision
  • puppet5 protected
  • puppet5_acs
  • puppet5_bookworm
  • puppet5_bnbarnes
  • erp_rhl
  • puppet5_spinto
  • puppet5-aptrefactor
  • master default protected
  • release/005.012
  • release/latest
  • release/005.010
  • release/005.009
  • release/005.008
  • release/005.007
  • release/005.006
  • release/005.005
  • release/005.004
  • release/005.003
  • release/005.002
  • release/005.001
  • release/005.000
  • release/004.063
  • release/004.062
  • release/004.060
  • release/004.059
  • release/004.058
  • release/004.057
  • release/004.056
28 results
Blame Permalink
  • Russ Allbery's avatar
    0693f68b
    Separate btmp and wtmp rotation · 0693f68b
    Russ Allbery authored 
    These files are supposed to have different permissions (0660 for
btmp and 0664 for wtmp), which isn't possible using a single united
base::newsyslog::config stanza.  Separate them into two stanzas
with the correct permissions.
    0693f68b
    History
    Separate btmp and wtmp rotation
    Russ Allbery authored 
    These files are supposed to have different permissions (0660 for
btmp and 0664 for wtmp), which isn't possible using a single united
base::newsyslog::config stanza.  Separate them into two stanzas
with the correct permissions.
TODO 677 B 
Cleanup code that can eventually be removed (with version when the cleanup
code was added):

- 001.002: base::newsyslog (removing /etc/newsyslog.weekly/audit)
- 001.002: base::newsyslog (removing /etc/newsyslog.monthly/wmtp)

The utility of these classes are somewhat questionable:

- base::newsyslog::disabled

  Can groups just not install base::newsyslog on servers that don't want
  it?  The problem was with other modules that assumed something would
  arrange for Package['newsyslog'] to be available and that install log
  rotation rules, but shouldn't those packages be separately ported to
  logrotate or the like and behave conditionally based on which is
  enabled?