I will give it a try.
touch /var/account/acct
accton
how long does it take for anything to get written to that file?
As far as fork storms, I did noticed 1. I had the junior admin write
a script to restart apache if LA got to high ....doing a truss on the pid
i did noticed mad processes and his perl script hitting 10% cpu at times.
Looking at it it was just a basic infinite while loop checking `uptime`.
I have taken that script off but I don;t think that is what is causing
this swap issue. Checking the hardware as well I have confirmed that
the manufacter for these machines only included a heat sink and this tiny
fan not big enough for these boxes....so cooling of the chip may be an
issue as well.....gonna have to check over a bunch of things next couple
days.
On Thu, 30 Aug 2001, mark tinguely wrote:
> Date: Thu, 30 Aug 2001 12:19:55 -0500 (CDT)
> From: mark tinguely <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: memory + apache
>
>
> > Yeah that is what I am thinking to. My guess is some large array allocated
> > in the php code maybe or a sql query taking to long to finish eating up
> > all the ram. That is kind of interesting to know.
>
> you said that the CPU usage spikes also at the time of the memory depletion?
> I wonder if you have some fork storm. If you had process accounting
> enabled and match it up with the web log file and vmstat activity you
> may be able to narrow your search.
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
