What we do is look for md0c to not respond.  When we reboot our system,
the process goes automatically to like 95 % and then throughout the
day/days, it creeps up to 100.

I am not sure how it was explained to me, but it has something to do
with memory and the boundaries that set.  

Does this make sense?

Dwane

-----Original Message-----
From: Atkins, Dwane P [mailto:ATKINSD at uthscsa dot edu] -
Sent: Monday, July 30, 2007 4:37 PM
To: Lee Sharp; m0n0wall at lists dot m0n0 dot ch
Subject: RE: [m0n0wall] Reboot

Lee,

Can what will this do for me?  And I pop it in the system section of the
m0n0wall service?

Thanks

Dwane

-----Original Message-----
From: Lee Sharp [mailto:leesharp at hal dash pc dot org] 
Sent: Monday, July 30, 2007 4:36 PM
To: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] Reboot

Atkins, Dwane P wrote:
> I have a question for the group.  We are running 1.23b on our
m0n0wall.
> We are getting a file system full error and a reboot seems to take
care
> of this.  Is there a way to schedule a reboot on m0n0wall for say like
3
> AM daily?

Are you filling up from the core dumps?  Pop this in your config in the 
system section.
"<shellcmd>sysctl kern.coredump=0</shellcmd>"

---------------------------------------------------------------------
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

---------------------------------------------------------------------
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