Bug #6035 | --tmpdir option for mysqld doesn't work or in my.cnf | ||
---|---|---|---|
Submitted: | 11 Oct 2004 19:10 | Modified: | 6 Jan 2005 20:53 |
Reporter: | Mark nielsen | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 4.1.5.-gamma | OS: | Linux (Linux) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[11 Oct 2004 19:10]
Mark nielsen
[11 Oct 2004 19:12]
Mark nielsen
Actually, the -t option doesn't work.
[11 Oct 2004 21:09]
MySQL Verification Team
Hi, Thank you for the report, but this is not a bug. Binary log files are stored in the MySQL datadir unless you specify path with --log-bin option. http://dev.mysql.com/doc/mysql/en/Binary_log.html
[13 Oct 2004 2:20]
Mark nielsen
I mistated the problem. It is not the binary logs, but when you do a mysqlimport, the binary logs has entries of the mysqlimport pointing to files in the /tmp directory. It is not the binary logs that get stored in /tmp but the files that the binary logs create in regards to a mysqlimport. Sorry.
[15 Oct 2004 3:34]
Matthew Lord
I'm not sure what you are referring to with the -t option. For mysqlbinlog this means that you want to see any later binlogs after the one you specify. Are you referring to the files created on a slave when doing load data infile and mysqlimport?
[6 Dec 2004 20:53]
Mark nielsen
The -t option was referring to temporary directories. Let me test if I am having the same problem with the latest version of MySQL 4.1.7. I remember I had some problems with the master database server putting files into /tmp rather than the temporary directory I specified. I will check this tonight or tommorrow.
[14 Feb 2005 22:54]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".