On Tue, Oct 09, 2012 at 04:20:14PM -0600, Stephen John Smoogen wrote: > > "If you have strict requirements on time-based logging rotation or > > certain audit requirements, then something like rsyslog(?) is required > > in parallel with the journal. In most other cases (desktops, tablets, > > many servers) the journal is sufficient." > *patch acked* Okay, so, given that: isn't systemd with time-based rotation logging more desirable than pushing that aspect off to rsyslog, because rsyslog loses the secure logging aspect? I would also note that the scope of organizations that have requirements for time-based rotation are much, much larger than than the set of organizations who need their servers to crash on error. It's an important use case, not just a thought experiment. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm@xxxxxxxxxxxxxxxxx> -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
