hey,
I just noticed a bizzare behavior on a box we recently built to upgrade a
legacy 32-bit 3.23 DB to 64-bit 4.0(.18) - explain this:
mysql@<hostname>:~> df -k /tmp
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda5 521748 42624 452620 9% /tmp
mysql@<hostname>:~> mysql -uroot -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 157997 to server version: 4.0.18-log
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> tee /tmp/wtf.tee;
Logging to file '/tmp/wtf.tee'
mysql> select now();
+---------------------+
| now() |
+---------------------+
| 2008-07-17 11:27:11 |
+---------------------+
1 row in set (0.00 sec)
mysql> notee;
Outfile disabled.
mysql> exit
Bye
mysql@oasdb3b00:~> df -k /tmp
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda5 521748 496240 0 100% /tmp
mysql@oasdb3b00:~> ls -l /tmp/wtf.tee
-rw-r--r-- 1 mysql mysql 464044032 2008-07-17 11:27 /tmp/wtf.tee
I don't have to use tee but it's handy and more importantly this makes me
wonder if I got a bad build and whether there's bigger mines out there I've
yet to step on...
| Thread |
|---|
| • tee command eating filesystem (4.0.18 64-bit) | Sid Lane | 17 Jul |
