Mike, I totally agree. The log solution wasn't my idea though <smile>.
No matter what language you write the script in, any type of ""Get some kind of response by throwing something against the server and seeing if it sticks"" response will get you the information you need. I set up a dummy account and use a simple shell with a "mysqladmin status" command. Works fine for me. This just lets me know whether the server is up or down. Your way would work well also, because if you have to get a "data response", it would probably provide greater detail as to the status and response time of the server. If not - hey what do I know <heh> Eric Lamendola At 10:26 AM 9/10/02 -0500, mos wrote: >Eric, > Isn't letting an outside connection access to your log file a > "little dangerous"? Why not create a dummy table with just one record in > it, restrict it to read access only, then use your chron job on a remote > computer to run a PHP/Perl script to access that record over the net. If > it returns an error, then examine the error number to determine what the > problem is. (Maybe the connection is down, or the database is down.) > There may be better ways to do it but this should be more secure. > >Mike --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
