On Wed, 15 Dec 2010, Peter M. Jansson wrote: > On Dec 15, 2010, [email protected] wrote: >> Serious potential irritant on a 32-bit box: a log file unexpectedly >> hits 2G, you don't have syslog configured to do anything special (like >> rotate it on a size limit...), and you lose data. > > I've seen two comments in this thread to the effect that 32-bit systems can't > handle files larger than 2G, and that's obviously wrong, as anyone who has > installed from a DVD ISO image knows. > > Is it syslog that has problems with files bigger than 2G? Or is this just > trying to apply a memory limitation to file storage?
the classic file I/O commands used a integer as the offset in the file, limiting you to 2G files. you can compile code with -LARGEFILE (or something similar), if you do so, and you only use the basic file I/O commands, you can then use files larger than 2G. However, if you do anything fancier in your application (where you remember offsets into files to do random access for example) then your application will have to be changed as the offsets won't fit in an integer any longer. David Lang _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
