ippool and cache-size
Konstantin Chekushin
koch2 at inbox.lv
Mon Sep 13 12:28:36 CEST 2010
Hi all. I have a question about rlm_ippool and cache-size option.
Info from description: cache-size: The gdbm cache size for the db
files. Should be equal to the number of ip's available in the ip
pool.
Also, note the cache size matches the number of IP's in your pool.
More is OK but wasteful, less is very bad.
My pool size is 32k. And I'm using this pool only for fallback
issue. So, I'll need it rarely in the future.
If cache-size = 32768, then radiusd process takes all memory.
"Mon Sep 13 12:33:46 2010 : Error: Couldn't fork: Cannot allocate
memory"
If cache-size = 16384 :
top:
PID USER PR NI VIRT
RES SHR S %CPU %MEM TIME+
COMMAND
3061 freerad 20 0 304m 261m 1080
S 0 52.1 0:00.00 radiusd
radiusd takes 261m! :-[ ]
So, here is my question. If I'll use default cache-size =800, and at
some point radius will start using this pool, what will happen if all
800 ip-addresses will be taken? Will the system slowdown, or if there
will be a segmentation fault or something else? Why is "less is very
bad"?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20100913/cb2bc953/attachment.html>
More information about the Freeradius-Users
mailing list