Hack 1: > Ran mysqldump against the production database, creating 1.txt Hack 2: > Ran mysqldump against the production database, creating 1.txt Anybody else

Hack 1: > Ran mysqldump against the production database, creating 1.txt Hack 2: > Ran mysqldump against the production database, creating 1.txt Anybody else sees a pattern here? We need to forbid creating files named "1.txt"!