Agreed that mysqlcheck is much more efficient... As for the timeout thing, I rememeber we were once using wget to run php scripts (which was not the correct way). Anyway, we had a script that was repeating every 15 minutes, and eventually we discovered that by default wget has a timeout of 15 minutes, and if it reaches that timeout, it will restart the script (thinking something went wrong), very bad implementation (of wget) in my opinion. As of then, we started running CRON php scripts without using wget. -- itoctopus - http://www.itoctopus.com "Jochem Maas" <jochem@xxxxxxxxxxxxx> wrote in message news:4608F1CB.3000601@xxxxxxxxxxxxxxxx > Tijnema ! wrote: > > On 3/26/07, Chris <dmagick@xxxxxxxxx> wrote: > >> itoctopus wrote: > >> > The purpose of this script is to optimize all associated tables in all > >> > databases on a mysql server. This script is working great, you can > >> put in a > >> > CRON and run it every day. Feel free to throw in your 2 cents! > >> > >> It's going to time out if you have any large databases or tables. > > php will not timeout on the commandline unless you actually specify > a timeout - unlike php as used as a webserver SAPI. > > > > > What about set_time_limit(999999)?? > > RTFM: set_time_limit(0); > > although it's not needed. > > > > >> > >> Also a much easier option is to run > >> > >> mysqlcheck -o ... > > indeed - use the right tool for the job. > > > > > That's true :) > > > > Tijnema > >> > >> -- > >> Postgresql & php tutorials > >> http://www.designmagick.com/ > >> > >> -- > >> PHP General Mailing List (http://www.php.net/) > >> To unsubscribe, visit: http://www.php.net/unsub.php > >> > >> > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
