Quote:
Originally posted by Trafficbrokercom
you are right .. but this would be a hassle for the admin .. he would need to set it back every time ..
have the payout cronjob starting at 5 am .. and the slave creates a dump at 4.59 am .. this would be the only way to cover the risk of temporary manipulation ..
another solution would be a monitoring script that creates a temp database that creates a snapshot x hours before payout and compares it with the table after payout ..
|
that's possible...currently we don't worry about it as only I and the owner have access, but we know someday we will need to delegate responsibility ot our team...that's why I wanted to checkout how these "detect mysql shaving" softwares worked...
Thx for the advice, Ive had that error before, but haven't had it in maybe 6 months now....replication been going smooth for us. I always think it's a good idea to upgrade to latest stables though =)
I'm waiting for MySQL's asynchronous replication. We were looking at using EMIC, but with MySQL's announcement we might as well wait for their own version