Analog doesn't stay resident; it does its job and quits. If analog comes up often on your server then either someone is logged in and running it, you have a web form that allows users to launch it, or it is being run regularly from a cron job or scheduled task.
When analog runs, it uses as much system power as it can to complete the job quickly. Log processing can often be a heavy burden. If your server is a Unix-variant you may be able to locate where the process is running and use the 'nice' command to reduce the server load. But notice that this may reduce responsiveness to users if someone is actively starting the process. -- Jeremy Wadsack Seven Simple Machines ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Charles Prakash Sent: Wednesday, January 10, 2007 2:19 PM To: [email protected] Subject: [analog-help] Regarding analog spike Hi Support, I am the owner of my own server(windows 2003). I have installed analog and it is working well but I don't know why analog.exe in the task manager spiking very often? which causing server overloading... Do you have any solution or how to kill the process? Is there any way to stop analog.exe by temporarily? Thanks in advance and I am looking forward your response. Regards, Charles. A
+------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Analog Documentation: http://analog.cx/docs/Readme.html | List archives: http://www.analog.cx/docs/mailing.html#listarchives | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general +------------------------------------------------------------------------
