Bug #3545 mysqlhotcopy should have a --passwordfile option
| Submitted: | 22 Apr 2004 14:25 | Modified: | 30 Nov 2009 14:31 |
|---|---|---|---|
| Reporter: | Tobias Burnus | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Command-line Clients | Severity: | S4 (Feature request) |
| Version: | 3.23.49, 5.1.x | OS: | Linux (Linux) |
| Assigned to: | CPU Architecture: | Any |
[22 Apr 2004 14:25]
Tobias Burnus
[22 Apr 2004 15:46]
Paul DuBois
If you want to put the password in a file, you can just use the standard technique of putting it in an option file. mysqlhotcopy reads the [client] and [mysqlhotcopy] groups, so you can use either of those.
[23 Apr 2004 1:32]
Tobias Burnus
> If you want to put the password in a file, you can just > use the standard technique of putting it in an option > file. mysqlhotcopy reads the [client] and [mysqlhotcopy] > groups, so you can use either of those. Well, for sure I don't want to put it into /etc/my.cnf since those settings should apply for all and the file is therefore world readable. (Somehow my mysqlhotcopy crashes if my.cnf is world-readable, though). Neither do I want to put the config into $SOMEUSER/.my.cnf. Thus instead of giving a passwordfile an option to give a configfile would be also fine with me.
[25 Apr 2004 22:45]
Sergei Golubchik
I'm not sure I understand why ~/.my.cnf wouldn't work for you. Anyway, the compatible way to do what you want is to use --defaults-extra-file command-line option that any mysql client is expected to support. mysqlhotcopy doesn't though - we'll consider adding this option to it.
[30 Nov 2009 14:31]
Valeriy Kravchuk
--default-extra-file option is still NOT supported by mysqlhotcopy command line utility: 77-52-12-228:5.1 openxs$ bin/mysqlhotcopy --defaults-extra-file=~/.my.cnf Unknown option: defaults-extra-file Invalid option bin/mysqlhotcopy Ver 1.23 ...
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.053 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.