I would have to agree with Bazsi. I've been running syslog-ng on Solaris 8 for a long while now and this never happened to me. It would pretty much have to be something on your system that is causing it. Regards, Drew -----Original Message----- From: Balazs Scheidler [mailto:bazsi@balabit.hu] Sent: Tuesday, January 28, 2003 2:46 AM To: syslog-ng@lists.balabit.hu Subject: Re: [syslog-ng]logs getting stomped on On Mon, Jan 27, 2003 at 11:10:48PM -0500, Brian Landers wrote:

...

This happened to me when I had the files on a filesystem that had a 2GB file size limit and I hit the 2GB limit.

Unfortunately, I'm reasonably sure this isn't the issue, unless syslog-ng itself has problems with large files. This is on Solaris 8, and the filesystem is mounted with the largefiles option:

/system on /dev/md/dsk/d50 read/write/setuid/intr/largefiles/logging/onerror=panic/dev=1540032 on Wed Aug 14 07:38:02 2002

Same thing happened again tonight, around the same time. At about 22:30, the log mysteriously was truncated and restarted. Arggh!!!

I think it should be something outside syslog-ng as I have never heard syslog-ng doing something like this (and I was listening carefully ;) -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html