Date: Wed, 13 Nov 2013 13:25:28 +0100 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= <trasz@FreeBSD.org> To: Ian Lepore <ian@FreeBSD.org> Cc: freebsd-hackers Hackers <freebsd-hackers@FreeBSD.org> Subject: Re: syslog(3) and truncated messages. Message-ID: <6B288F99-5AEF-4F63-9ACD-00307A5CA472@FreeBSD.org> In-Reply-To: <1384304775.31172.356.camel@revolution.hippie.lan> References: <F6847F26-2959-4F9C-8EC6-CFCDACBC2092@FreeBSD.org> <1384304775.31172.356.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Wiadomo=B6=E6 napisana przez Ian Lepore w dniu 13 lis 2013, o godz. = 02:06: > On Tue, 2013-11-12 at 23:00 +0100, Edward Tomasz Napiera=B3a wrote: >> I have a daemon (namely ctld(8)) that, when running with debug = enabled, >> outputs a lot of information to the syslog, using the usual syslog(3) = API. >> Problem is, the output gets truncated: at some point the log messages >> from all involved processes stop getting logged, even though the = processes >> continue to run, confirmed by subsequent kernel messages, which get = logged >> properly. >>=20 >> Any idea what might be going on? >>=20 >=20 > It turns out I had newer patches that did apply cleanly for this, so I > committed them as r258076 and r258077 (since they really addressed two > completely separate items). >=20 > Hopefully this will fix the glitches you're seeing. Yes, the problem seems to be fixed. Thanks! --=20 If you cut off my head, what would I say? Me and my head, or me and my = body?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6B288F99-5AEF-4F63-9ACD-00307A5CA472>