On 9 October 2012 15:24, Lennart Poettering <mzerqung(a)0pointer.de> wrote:
On Tue, 09.10.12 16:53, Simo Sorce (simo(a)redhat.com) wrote:
If you want audit-like semantics with crashing if we cannot write,
then
use something else, not the journal. The journal is supposed to be
robust and do the right thing so that you can leave it unnatteneded and
whatever happens it didn't spill the disk or become unavailable. It's
supposed to be "zero maintainance".
So in those cases rsyslog would be required, but would be seen as a
post-install step.
EG what you are looking at is building a GNOME-OS and for those sorts
of tablets, etc the journal is right for that. The other cases like at
a Hospital, trading firm or various .gov.XX then having rsyslog
installed with audit post would be the way to get the needed features.
--
Stephen J Smoogen.
"Don't derail a useful feature for the 99% because you're not in it."
Linus Torvalds
"Years ago my mother used to say to me,... Elwood, you must be oh
so smart or oh so pleasant. Well, for years I was smart. I
recommend pleasant. You may quote me." —James Stewart as Elwood P. Dowd