[snip] > > I think the trick is defining _FILE_OFFSET_BITS = 64. > > Yes, I found after sending the letter. But since this only works when > you compile the program yourself, and the database acording to the > support should not suffer from this limit, I thought maybe there was > some magic flip I had to switch. Some key that made lseek syscalls use > the 64-bit version if available or something like that. Perhaps some > missing links from src/include(lib) to kernel-src/include(lib) or some > other issue I'd missed. > > I guess I have to talk to the support again, preferably som low-level > supporter. > > Thanks for the replies, I appreciate it a lot.
Apparently it is a compile time feature. Basically substituting lseek64, open64, etc.. for the 32 bit variants. No way to change that after the code has been built... -- Eric G. Miller <egm2@jps.net>
