I don't meant the problem is IN 32-bit CPUs but in kernel filesystem drivers, libc, and VFS layer WHERE you are using 32bits CPUs. Of course you can deal with large filesystems, to the fact that you can deal with XFS for example.
That test is quite vague. try it: dd if=/dev/zero of=bigfile bs=1024 count=3145728 dd if=/dev/zero of=bigfile bs=1024 count=5145728 dd if=/dev/zero bs=1024 count=5145728 > bigfile If you are really worried about the limit, you should see LFS (Large File Summit). (I'm part of the devolepment and i can help you if you need, but i think you don't need ;) ) If you only need large file support in kannel, you should (probably you need some code changes) recompile using D_FILE_OFFSET_BITS=64 M On 06 Sep 2006 15:54:06 +0200, Guillaume Cottenceau <[EMAIL PROTECTED]> 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/
