Guest Marius Homs Posted September 3, 2008 Posted September 3, 2008 Hello, I manage a webserver and to keep track of the performance and stability of this machine, I've created a Counterlog. This log writes it's data to a SQL database 24/7. Now and then the counterlog just stops. How can I make sure it will always keep running and it restarts itself when it is stopped? When the server is rebooted the log starts, so that's not the problem. I think it has something to do with loosing the connection to the database, but I have no proof for this. But when that db-connection is lost, or something else makes the log stop: how should I configure the log so that is starts again? I have scheduled it to start manually and stops after 9999 days, so it should not be allowed to stop! Thanks in advance! Marius
Recommended Posts