Bug#387109: Processed: Re: Bug#387109: Does ulog-acctd support logfile > 2GB ?

severity 418430 whishlist tags 418430 - patch lfs severity 387109 normal tags 387109 + patch lfs thanks Sorry about that... wrong copy/paste. Regards, -- Clément Hermann (nodens) - "L'air pur ? c'est pas en RL, ça ? c'est pas hors charte ?" Jean in L'Histoire des Pingouins, http://tnemeth.fre

Bug#387109: Does ulog-acctd support logfile > 2GB ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 severity 418430 normal tags 418430 + patch lfs thanks Hi, I can confirm that adding -D_FILE_OFFSET_BITS=64 to the CFLAGS fixes the problem. (trivial) patch attached. Meanwhile, those interested will find fixed source and i386 binary on http://cle

Bug#387109: Does ulog-acctd support logfile > 2GB ?

Fabrice LORRAIN <[EMAIL PROTECTED]> writes: Please try adding -D_FILE_OFFSET_BITS=64 to src/Makefile and recompiling the package. Cheers, -Hilko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#387109: Does ulog-acctd support logfile > 2GB ?

Fabrice LORRAIN <[EMAIL PROTECTED]> writes: > Hence my question, Does ulog-acctd support manipulating >2GB log > files. Comments ? Sorry, I don't know. Probably not. It's one of those cases where I would have said "2 gigs fo logfiles should be enough for everybody" if somebody had brought up that

Bug#387109: Does ulog-acctd support logfile > 2GB ?

Package: ulog-acctd Version: 0.4.3-2 Severity: wishlist Hello Hilko, Following a viral attack on our campus, ulog-acctd add difficulties logging the flows. The weird stuff is that the log file got truncated at 2GB (and ulog-acctd generated >4000 account.log.write. hardlink files). I checked