Hi:
This is NOT a problem with Links per se, but involved with it. I have made a few mods... and something is not right somewhere. I am SURE the problem is with something I wrote.... but I cannot track it down, and I was hoping someone might know how I could.
Every now and again (1-3 times an hour, it seems), something goes into a loop, gobbles up memory and CPU. Because it happens so unoften, I know it is not one of the major processes (jump, page, etc), and I guess it is something that only get's called very occasionally. Possibly bad code in a global (although I proffed all those last night, found nothing...) or one bad Link... I view top, and all I can tell is the PID (which does not help) and it is a httpd process. If I knew exactly the page called (with paramaters), I could find the problem easily. Is there some way I can find out the script or the page being viewed that starts this runaway process?
Currently, I have the RMemLOAD (?- something like that) set to 40 megs, so it keeps them from running wild... but the process is still in limbo, so I restart httpd every hour to kill them. But I would really like to find the bad code and fix it.
Any ideas?
thanks!
dave
dave
Big Cartoon DataBase
Big Comic Book DataBase
This is NOT a problem with Links per se, but involved with it. I have made a few mods... and something is not right somewhere. I am SURE the problem is with something I wrote.... but I cannot track it down, and I was hoping someone might know how I could.
Every now and again (1-3 times an hour, it seems), something goes into a loop, gobbles up memory and CPU. Because it happens so unoften, I know it is not one of the major processes (jump, page, etc), and I guess it is something that only get's called very occasionally. Possibly bad code in a global (although I proffed all those last night, found nothing...) or one bad Link... I view top, and all I can tell is the PID (which does not help) and it is a httpd process. If I knew exactly the page called (with paramaters), I could find the problem easily. Is there some way I can find out the script or the page being viewed that starts this runaway process?
Currently, I have the RMemLOAD (?- something like that) set to 40 megs, so it keeps them from running wild... but the process is still in limbo, so I restart httpd every hour to kill them. But I would really like to find the bad code and fix it.
Any ideas?
thanks!
dave
dave
Big Cartoon DataBase
Big Comic Book DataBase
