-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2013-05-10 at 13:20 -0400, Anton Aylward wrote:
Under my desk is one of the crapped out 800Mhz box from the Closet of Anxieties. Its running a DNS server for the other such boxes. The DNS loads a huge set from http://pgl.yoyo.org/as/serverlist.php This morging I watched it load and saw ...
Feb 8 10:04:33 server named-checkconf[1810]: zone ad2.lupa.cz/IN: loaded serial 2012100600 Feb 8 10:04:33 server named-checkconf[1810]: zone ad2.mamma.com/IN: loaded serial 2012100600 Feb 8 10:04:33 server rsyslogd-2177: imuxsock begins to drop messages from pid 1810 due to rate-limiting Feb 8 10:04:35 server rsyslogd-2177: imuxsock lost 268 messages from pid 1810 due to rate-limiting
Even this crappy old machine can outpace the syslog daemon writing to a text file.
No, that's a known issue and it is solvable, either with an update or an adjusting of your settigns. I reported about that problem here: Date: Wed, 12 Sep 2012 17:14:03 +0200 (CEST) From: Carlos E. R. <> Subject: [opensuse] rsyslog drops thousands of messages. And my machine is powerful enough, yet it was dropping thousands of messages - not because CPU or i/o limits.
Now some of my clients are using syslog to monitor networks of hundreds of machines. And in order to mine the data they are sticking it into a database so they can perform queries on it, ones that are more involved than you can do with grep and regular expressions.
Text files can't cut it any more.
syslog can use databases, too. Just configure it. I also worked sometime for a company that sold a very expensive product that stored text output from logs into databases, producing alarms and usefull things. Hugely expensive... and inefficient. We could find stuff sooner with a PC running Linux and grepping the original text files, than the very expensive machine with expensive software was using. But heck, what we used could not be talked about, or the business from the big official product wuld plummet, and we would not get our salaries! >:-P
Well, that's not an ABSOLUTE. Those examples are about high volumes that need to be accessed fast and randomly. (Rather like a disk, eh? So use the BtrFS!)
Reiserfs was designed to operate like a database. It was to be done for real in version 4, you could add your own modules. Pity.
Perhaps the debate should be about human intelligible vs machine optimized text files. The style used in systemd, xinit, xorg.conf are documented externally but allows for in-line comments, something I sorely miss when dealing with things like Windows registry. The XML format has the semantics documented elsewhere, hopefully, with the DTD, but how much semantic for the human is there in that?
Human manageable configuration text files have their place.
Indeed! :-) - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGRQmEACgkQtTMYHG2NR9V5+wCeMw66jrh8Tqc5eumVLh931KWT GqgAnAoQ6wASv66rloZmnjY2sSlhp5IQ =v4N+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org