On Fri, 2002-11-08 at 01:41, Balazs Scheidler wrote:
On Thu, Nov 07, 2002 at 01:27:52PM -0800, Nathan wrote:
i keep getting this error every time i try and start syslog-ng the system is redhat linux 2.4.18. any clues on why i'm getting this? thanks.
io.c: Preparing fd 3 for reading io.c: listening on fd 4 syslog-ng version 1.4.17 starting gc_mark: Marking object of class 'syslog_backend' (0) gc_mark: Marking object of class 'syslog_config' (1) gc_mark: Marking object of class 'resource_list' (2) gc_mark: Marking object of class 'log_source_group' (2) gc_mark: Marking object of class 'afunix_source' (3) gc_mark: Marking object of class 'log_connection' (16) gc_mark: Marking object of class 'log_endpoint_info' (17) gc_mark: Marking object of class 'log_endpoint_info' (18) gc_mark: Marking object of class 'log_endpoint_info' (19) gc_mark: Marking object of class 'log_connection' (17) gc_mark: Marking object of class 'log_endpoint_info' (18) gc_mark: Marking object of class 'log_endpoint_info' (19) gc_mark: Marking object of class 'log_endpoint_info' (20) gc_mark: Marking object of class 'afsocket_source_close_callback' (6) gc_mark: Marking object of class 'unix_address_info' (4) gc_mark: Marking object of class 'object_queue' (4) gc_mark: Marking object of class 'log_source_driver' (4) io.c: Preparing fd 5 for reading io.c: Preparing fd 6 for writing io.c: Preparing fd 7 for writing io.c: Preparing fd 8 for writing File size limit exceeded
does the program exit in this case? it seems that syslog-ng gets a SIGXFSZ signal:
SIGXFSZ 25,25,31 C File size limit exceeded (4.2 BSD)
did syslog-ng detect O_LARGEFILE during configure? does your filesystem support 64 bit file sizes?
yep exits every time with the same error. as far as i can tell O_LARGEFILE was not detected during configure and it seems thats my filesystem (ext3 on redhat 7.3) supports 64 bit files sizes. -- Nathan <nathank@netflip.com>