sean finney wrote: > perhaps you still have the old version of the cron script? > unfortunately i don't have access to the svn repository right now, > but i'll send you a copy of the the "default" version to see > if there are any differences as soon as i do, probably this > evening. in the meantime, there has just been another update > to mysql-dfsg-4.1 that includes another binary log-related problem. > while i don't think it's the same issue, maybe upgrading will let you > know if the file has changed (giving you the standard "this file has > changed" warning), or maybe the problem will otherwise go away :) >
I upgraded to the new 4.1.15-1 mysql-server4.1 and there were definitely differences in the cron files: < if ! echo 'SHOW MASTER LOGS;' | $M --skip-column-names >$tmp 2>&1; then --- > if ! echo 'SHOW MASTER LOGS;' | $M --skip-column-names 2>&1 | cut -f1 >$tmp; then The new script works. This may be a fault done by me because normally I do not change a configuration file which is given the "file has changed warning" on upgrades. Maybe a better strategy would be to hold back self edited files only (and look into a new file diff anyway). Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
