Date: Tue, 4 Sep 2012 10:26:03 +0400 From: Eygene Ryabinkin <rea@freebsd.org> To: Attilio Rao <attilio@freebsd.org> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: syslog(3) issues Message-ID: <MPWI/79FQ3zZ8Hg2fK4h6jbnkzU@OEL%2BAGsq2qOfta3tVB3M%2BFMK4kc> In-Reply-To: <CAJ-FndDeNVcEv5HRBMtQ5ZKa3zdWwt5d4fFPaoXnyV3MS31QDw@mail.gmail.com> References: <CAJ-FndDeNVcEv5HRBMtQ5ZKa3zdWwt5d4fFPaoXnyV3MS31QDw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--6CiRFyVmOOJ3DkBX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Attilio, good day. Mon, Sep 03, 2012 at 12:35:24AM +0100, Attilio Rao wrote: > I was trying to use syslog(3) in a port application that uses > threading , having all of them at the LOG_CRIT level. What I see is > that when the logging gets massive (1000 entries) I cannot find some > items within the /var/log/messages (I know because I started stamping > also some sort of message ID in order to see what is going on). The > missing items are in the order of 25% of what really be there. >=20 > Someone has a good idea on where I can start verifying for my syslogd > system? This is almost obvious, but had you tried running syslogd with flag '-d' that gives verbose information about incoming stuff and whether it will be logged to some file(s). --=20 Eygene Ryabinkin ,,,^..^,,, [ Life's unfair - but root password helps! | codelabs.ru ] [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ] --6CiRFyVmOOJ3DkBX Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iF4EABEIAAYFAlBFnvsACgkQFq+eroFS7PugiQD/Vau1xGchpWZU1/7w0wp1lws5 VruVRFWVUwAJKzJwY/UA/0QEiBoJ6AvGtmDjT6xQaKXXQdla00Fb3//gNppukdAo =gskw -----END PGP SIGNATURE----- --6CiRFyVmOOJ3DkBX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?MPWI/79FQ3zZ8Hg2fK4h6jbnkzU>