[syslog-ng]logs getting stomped on

[Brian Landers]

> 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=3Dpanic/dev=3D1540032 =
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!!!


--=20
Brian Landers                     |  packetslave@sapient.com
Network System Exorcist           |  vox://404/439.4117
Sapient Information Technology    |  aim://Bluecoat93
CCNA, SCSA, EIEIO                 |  yim://brian_landers

"Trust your family to have a Bottomless Pit, Malfoy," said Harry=20
darkly. "Other people have shrubbery in the garden. You have a=20
Bottomless Pit."=20