RE: radwtmp 2GB file size limit
Apache also dies when it hits the 2GB limit for a log file, so maybe it is an unwritten FS limit? -Drew -Original Message- From: Christian Balzer [mailto:[EMAIL PROTECTED] Sent: Thursday, July 29, 2004 9:11 AM To: [EMAIL PROTECTED] Subject: radwtmp 2GB file size limit Hello, the subject says it all and pretty much also sums up how I searched the archive to see if this was previously reported. If it escaped my search, sorry. This is Debian Sarge, thus freeradius 0.9.3. When the radwtmp file reaches 2GB freeradius dies w/o any trace in the logs, so it took me a few minutes to figure out what was going on. The OS/kernel/filesystem are NOT the limiting factor. I'm not sure what the desired behavior should be, as in to support larger files or terminate with klaxon sounds and warnings all over the logs and stderr, but clearly the current state of affairs leaves something to be desired. Though there are probably no security implications. Regards, Christian Balzer -- Christian BalzerNetwork/Systems EngineerNOC [EMAIL PROTECTED] Global OnLine Japan/Fusion Network Services http://www.gol.com/ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: radwtmp 2GB file size limit
On Thu, 29 Jul 2004, Christian Balzer wrote: Hello, the subject says it all and pretty much also sums up how I searched the archive to see if this was previously reported. If it escaped my search, sorry. This is Debian Sarge, thus freeradius 0.9.3. When the radwtmp file reaches 2GB freeradius dies w/o any trace in the logs, so it took me a few minutes to figure out what was going on. The OS/kernel/filesystem are NOT the limiting factor. I'm not sure what the desired behavior should be, as in to support larger files or terminate with klaxon sounds and warnings all over the logs and stderr, but clearly the current state of affairs leaves something to be desired. Though there are probably no security implications. Recompile freeradius. In configure pass the option --with-large-files (by default it's not set). Regards, Christian Balzer -- Christian BalzerNetwork/Systems EngineerNOC [EMAIL PROTECTED] Global OnLine Japan/Fusion Network Services http://www.gol.com/ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html -- Kostas Kalevras Network Operations Center [EMAIL PROTECTED] National Technical University of Athens, Greece Work Phone: +30 210 7721861 'Go back to the shadow' Gandalf - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: radwtmp 2GB file size limit
Kostas wrote: Recompile freeradius. In configure pass the option --with-large-files (by default it's not set). I got hand rolled and Debian package freeradius servers , so I could do that. Though for maintainability reasons I prefer packages whenever possible. And in the end a silent death is never a good thing, IMHO. That said, is there anything that will make a freeradius compiled with that flag incompatible to a normal one? Because if so, that is where the Debian package maintainer will balk (same reason why INN is not compiled --with-large-files for Debian). Regards, Christian Balzer -- Christian BalzerNetwork/Systems EngineerNOC [EMAIL PROTECTED] Global OnLine Japan/Fusion Network Services http://www.gol.com/ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: radwtmp 2GB file size limit
Apache also dies when it hits the 2GB limit for a log file, so maybe it is an unwritten FS limit? No, your Apache is not compiled with large files support (LSB). If you compile your own Apache ./configure it like this (if I remember corectly): CFLAGS='-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64' ./configure ... If you use a packaged Apache complain to your source of packages. -- damjan | This is my jabber ID -- [EMAIL PROTECTED] -- not my mail address!!! - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
