Lee,

Are you sure the log size matters?  I had mine set to "999" and for a test 
changed it to "50" and rebooted but the free space of "/dev/md0c" stayed the 
same.

Roy...

----Original Message Follows----
From: "Lee Sharp" <leesharp at hal dash pc dot org>
To: "m0n0wall" <m0n0wall at lists dot m0n0 dot ch>
Subject: Re: [m0n0wall] Cannot get IP from DHCP. Need help.
Date: Sun, 13 Aug 2006 12:00:03 -0500

From: "Ervin Malicdem" <schadow1 at gmail dot com>

>I got the full filesystem again and take note I only have 3 dhcp
>clients leasing.
>What could be wrong?

>$ df -h
>Filesystem   Size   Used  Avail Capacity  Mounted on
>/dev/md0c     11M    11M    13K   100%    /
>procfs       4.0K   4.0K     0B   100%    /proc
>/dev/ad0a    6.7M   5.5M   1.2M    82%    /cf

A real problem requiring thought this early Sunday morning...  And before 
coffee...  Lets start with definitions.  That may also get my thoughts 
straight.

/dev/md0c is your ram disk.  It is statically created at boot.  It does not 
grow.  It holds leases, databases, arp tables, log files...  Something has 
you full.  128 is enough ram, but the files system is 11 meg whatever you 
have. Lets start with what services are you running?  How long are your 
logs? (Over 50 takes space fast)  Do you have a complex captive portal page 
with a lot of images?

/dev/ad0a is your drive image. (Hard drive or CF)  The image size is also 
static, so Andrew is confused. :-)  The important thing is that nothing is 
saved here.  The only time this is opened for writing is to save the 
config.xml or to upgrade firmware.

So look at your log files.  Also look around your file system at /var/log 
and see what is big.  Nothing there should be over 256k.

                        Lee


---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch