From: Joe Z. <joe...@za...> - 2005-01-26 00:19:46
|
Manfred Rebentisch wrote: >Am Montag, 17. Januar 2005 07:39 schrieb Joe Zacky: > > >>It's been working very well the past week. I get a short email after >>each backup, if it failed I take a look at bobs.log to see why. I've >>done the smb and rsync-ssh templates, still need to do the others. I'm >>also looking into some other errors I see in bobs.log, mostly having to >>do with stat() and is_dir() on very large files failing while building >>the indexes after the backup has run. It seems it's a libc or glibc >>problem, but I need to handle the failure properly in the script. >> >> >> > >This is a problem of PHP. The PHP-Engine and all add-ons have to be compiled >with the Option -D _FILE_OFFSET_BITS=64 . >Without this option the stat member st_size (type off_t) has only 32 Bit. > >I did not know, if we can compile PHP with this option, because there are more >changes needed (or the developers were very strong while using types). > >The glibc does support it very well. > >Manfred > > I'm not doubting you, nor do I pretend to understand anything about libc/glibc. This link is where I got my information. Please take a look at it. http://bugs.php.net/bug.php?id=27765 It won't change how I handle the error because whether it's a php or libc problem, the error has to be handled in the php script. I can't expect everyone that uses bobs to patch their libc and/or rebuild php. Joe |