Re: Logfiles above 2G

use of syslog is optional. I dont compile it with syslog as I want to  
have separate logfiles.
my small test C programm shows that normal compilation hits this wall.
But if I open the file with fopen64, then it works. Rather strange as  
Linux seems to be the only OS where this has been done like that.

I'll check what the currentl CVS does about this.

-D_FILE_OFFSET_BITS=64 is not working here.
will verify with -D_LARGE_FILES. Also I found similar names (but not  
same) in the headerfiles.
This was tested on Fedora5.



On 06.09.2006, at 15:54, Guillaume Cottenceau wrote:

> Andreas Fink <andreas 'at' fink.org> writes:
>
>> However if kannel's gwlib runs in full debug mode and the logfile
>> hits 2GB, the application quits/stops working and when you relaunch
>> it, it appends to the same 2GB logfile and quits again because it
>> cant go beyond this 2GB limit.
>
> "log.c" seems to be able to use syslog, so on Linux at least it
> should use syslog and have no file limit or log rotation problem.
> I'm rather confused.
>
> -- 
> Guillaume Cottenceau
> Create your personal SMS or WAP Service - visit http:// 
> mobilefriends.ch/