relay log file maintenance problem

I have a replication server that is running out of disk space because of old relay binary log files. Both it and the master server are version 4.0.20. I have a cron script that maintains a 3 day history of binary log files on the master server. Has someone figured out a way to manage the

Table doesn't exist on query replication problem...

it has no concept of the database named reporting. Is there a way to rework this query so that either there are no references to the reporting database or to configure my.cnf on the master and slave to handle this query? Thanks in advance, -Bill Thomason -- MySQL General Mailing List For list

Replication problem with a cross database query

relationships and uncovered the bug in doing so. Thanks in advance, -Bill Thomason -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

In replication, can you have a slave act as a master to a different slave?

Here is my scenario: I have 3 linux boxes - 2 with mysql 4.0.16 and 1 with 4.0.17. I have a 4.0.16 master (sys1) replicating a database (db1) that is roughly 1.5GB to a slave system (sys2) running 4.0.17. For the sake of a formal representation I'll say that (sys1,db1) -- (sys2,db1)