*** From dhcp-server -- To unsubscribe, see the end of this message. ***
I've searched through the archives trying to find out how much memory
the dhcp server should be using and the closest I can find is about
144 bytes per lease.
The reason I'm looking is because I am losing "free" memory in a big
way on this computer (rh linux 5.2, 64M of RAM) and nothing else (out
of the ordinary) is running besides dhcpd. I restarted the server at
about 11:30 this morning, ran top and saw that I had 46M of free RAM.
It's about 4 hours later and I'm down to about 36M. It'll keep
dwindling if I let it go. Has anyone else noticed any memory problems
with v2pl18? I ran v2pl6 on this machine (rh linux 4.2 with 32M) for
the longest time and never had any memory problems. I have another
computer, same exact configuration (rhl5.2,64M), the only difference
being that it is not running dhcpd and the free memory has been stable
at 50M during this same period of time.
I did recently increase the number of subnets and ranges by about 3
times what it was, but using some perl scripts that have been posted
here in the past, it looks like I only have about 800 active leases
(using the above mentioned 144 bytes, this only translates to about
120K, not 10+M). I'm not big into programming, but this looks like a
pretty big memory leak somewhere. And, since my other machine is
solid as a rock, I'm guessing that it's dhcpd. Can anyone give me
some pointers to figure out what's happening to all of my memory?
Below is a copy of everything that is currently running:
$ ps aux | sort | more
USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND
bin 211 0.0 0.5 752 320 ? S 11:26 0:00 portmap
hpassaue 290 0.0 1.2 1224 796 1 S 11:26 0:00 -bash
hpassaue 299 0.0 1.2 1228 804 p0 S 11:28 0:00 -bash
hpassaue 322 0.8 1.1 1160 712 1 S 11:29 1:43 top -s
hpassaue 346 0.0 0.7 852 484 p0 R 14:45 0:00 ps aux
hpassaue 347 0.0 1.2 1228 804 p0 R 14:45 0:00 -bash
hpassaue 348 0.0 1.2 1228 804 p0 R 14:45 0:00 -bash
root 1 0.0 0.6 776 404 ? S 11:25 0:02 init [3]
root 2 0.0 0.0 0 0 ? SW 11:25 0:00 (kflushd)
root 3 0.0 0.0 0 0 ? SW< 11:25 0:00 (kswapd)
root 4 0.0 0.0 0 0 ? SW 11:25 0:00 (md_thread)
root 5 0.0 0.0 0 0 ? SW 11:25 0:00 (md_thread)
root 36 0.0 0.5 736 364 ? S 11:26 0:00 /sbin/kerneld
root 222 3.5 0.6 796 428 ? R 11:26 7:01 syslogd
root 231 0.0 0.6 776 388 ? S 11:26 0:00 klogd
root 242 0.0 0.7 852 472 ? S 11:26 0:00 crond
root 253 0.0 0.6 772 396 ? S 11:26 0:00 inetd
root 270 0.0 1.4 1404 916 ? S 11:26 0:00 sendmail: accepting c
root 288 0.3 5.7 4052 3652 ? S 11:26 0:39 /usr/sbin/dhcpd
root 291 0.0 0.4 724 296 2 S 11:26 0:00 /sbin/mingetty tty2
root 292 0.0 0.4 724 296 3 S 11:26 0:00 /sbin/mingetty tty3
root 293 0.0 0.4 724 296 4 S 11:26 0:00 /sbin/mingetty tty4
root 294 0.0 0.4 724 296 5 S 11:26 0:00 /sbin/mingetty tty5
root 295 0.0 0.4 724 296 6 S 11:26 0:00 /sbin/mingetty tty6
root 297 0.0 0.3 720 228 ? S 11:26 0:00 update (bdflush)
root 298 0.0 1.0 1228 688 ? S 11:28 0:00 in.telnetd
_ . | Trust the computer industry to
|_) || [EMAIL PROTECTED] | shorten "Year 2000" to Y2k. It was
|_)||||_| | this kind of thinking that caused
Passauer_| Residence Computing | the problem in the first place.
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
------------------------------------------------------------------------------
