blocks|key|167362|text|如果您的MySQL客户端/服务器版本是5.6.x，避免出现警告消息的方法是使用工具：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|167363|mysql_config_editor+set+--login-path=local+--host=localhost+--user=username+--password|code-block|syntax|javascript|167364|然后，您可以在shell脚本中使用：|167365|mysql+--login-path=local++-e+"statement"|167366|而不是：|167367|mysql+-u+username+-p+pass+-e+"statement"|167368|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

If your MySQL client/server version is a 5.6.x a way to avoid the WARNING message are using the <a href="http://dev.mysql.com/doc/refman/5.6/en/mysql-config-editor.html" rel="noreferrer">mysql_config_editor</a> tools:

<pre><code>mysql_config_editor set --login-path=local --host=localhost --user=username --password
</code></pre>

Then you can use in your shell script:

<pre><code>mysql --login-path=local -e "statement"
</code></pre>

Instead of:

<pre><code>mysql -u username -p pass -e "statement"
</code></pre>

blocks|key|2764099|text|另一种选择是使用sshpass调用mysql，例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2764100|sshpass+-p+topsecret+mysql+-u+root+-p+username+-e+'statement'|code-block|syntax|javascript|2764101|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Another alternative is to use sshpass to invoke mysql, e.g.:

<pre><code>sshpass -p topsecret mysql -u root -p username -e 'statement'
</code></pre>

blocks|key|169080|text|还可以在指定登录路径时，在脚本中运行mysql_config_editor以传入口令|type|unstyled|depth|inlineStyleRanges|entityRanges|data|169081|expect+-c+"
spawn+mysql_config_editor+set+--login-path=$mySqlUser+--host=localhost+--user=$mySqlUser+--password
expect+-nocase+\"Enter+password:\"+{send+\"$mySqlPassword\r\";+interact}
"|code-block|syntax|javascript|169082|这将启动一个expect会话，可在脚本中使用该会话与提示进行交互|169083|See+this+post|offset|length|169084|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/10606958/how-do-i-automatically-input-a-password-when-i-run-a-bash-script^0|0|0|0|0|D|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

You can also run the mysql_config_editor in your script to pass in the password when specifying the login path

<pre><code>expect -c "
spawn mysql_config_editor set --login-path=$mySqlUser --host=localhost --user=$mySqlUser --password
expect -nocase \"Enter password:\" {send \"$mySqlPassword\r\"; interact}
"
</code></pre>

This starts an expect session which can be used in scripts to interact with prompts

<a href="https://stackoverflow.com/questions/10606958/how-do-i-automatically-input-a-password-when-i-run-a-bash-script">See this post</a>

blocks|key|165332|text|最简单的方法是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|165333|mysql+-u+root+-pMYPASSWORD+-e+"show+databases"+2>/dev/null|code-block|syntax|javascript|165334|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Easiest way is 

<pre><code>mysql -u root -pMYPASSWORD -e "show databases" 2&gt;/dev/null
</code></pre>

blocks|key|166426|text|我使用类似这样的东西：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|166427|mysql+--defaults-extra-file=/path/to/config.cnf|code-block|syntax|javascript|166428|或|166429|mysqldump+--defaults-extra-file=/path/to/config.cnf+|166430|其中，config.cnf包含：|166431|[client]
user+=+"whatever"
password+=+"whatever"
host+=+"whatever"|166432|这允许您拥有多个配置文件-用于不同的服务器/角色/数据库。使用~/.my.cnf将只允许您拥有一组配置(尽管它可能是一组有用的默认值)。|166433|如果您使用的是基于Debian的发行版，并以root身份运行，则可以跳过上述步骤，只需使用/etc/mysql/debian.cnf进入...：|166434|mysql+--defaults-extra-file=/etc/mysql/debian.cnf|offset|length|style|CODE|166435|entityMap^0|0|0|0|0|0|0|0|0|0|1D|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|17|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|18|8|@$U|19|V|1A|W|X]]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Z|$]]

I use something like:
<pre><code>mysql --defaults-extra-file=/path/to/config.cnf
</code></pre>
or
<pre><code>mysqldump --defaults-extra-file=/path/to/config.cnf 
</code></pre>
Where config.cnf contains:
<pre><code>[client]
user = &quot;whatever&quot;
password = &quot;whatever&quot;
host = &quot;whatever&quot;
</code></pre>
This allows you to have multiple config files - for different servers/roles/databases. Using ~/.my.cnf will only allow you to have one set of configuration (although it may be a useful set of defaults).
If you're on a Debian based distro, and running as root, you could skip the above and just use /etc/mysql/debian.cnf to get in ... :
<code>mysql --defaults-extra-file=/etc/mysql/debian.cnf</code>

blocks|key|166467|text|一种方便(但同样不安全)的方法是使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|166468|MYSQL_PWD=xxxxxxxx+mysql+-u+root+-e+"statement"|code-block|syntax|javascript|166469|166470|请注意，官方文档建议不要使用它。|166471|请参阅6.1.2.1+End-User+Guidelines+for+Password+Security+(Mysql+Manual+for+Version+5.6)|offset|length|166472|166473|+将密码存储在+MYSQL_PWD+环境变量中|blockquote|style|BOLD|CODE|166474|166475|这种指定MySQL密码的方法必须被认为是极不安全的，不应该使用。某些版本的ps包含一个选项，用于显示运行进程的环境。在某些系统上，如果设置了MYSQL_PWD，则您的密码将向运行ps的任何其他用户公开。即使在没有此版本ps的系统上，假设没有其他方法可供用户检查进程环境也是不明智的。|166476|entityMap|0|LINK|mutability|MUTABLE|url|http://dev.mysql.com/doc/refman/5.5/en/password-security-user.html^0|0|0|0|0|3|28|0|0|0|1|6|8|9|I|4|8|9|0|0|11|2|2H|2|31|2|1Y|9|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|16|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|18|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@$L|1A|M|1B|1|1C]]|A|$]]|$1|N|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1E|8|@$L|1F|M|1G|R|S]|$L|1H|M|1I|R|S]|$L|1J|M|1K|R|S]|$L|1L|M|1M|R|T]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1O|8|@$L|1P|M|1Q|R|S]|$L|1R|M|1S|R|S]|$L|1T|M|1U|R|S]|$L|1V|M|1W|R|T]]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]]|Y|$Z|$5|10|11|12|A|$13|14]]]]

One method that is convenient (but equally insecure) is to use:
<pre><code>MYSQL_PWD=xxxxxxxx mysql -u root -e &quot;statement&quot;
</code></pre>
<hr />
Note that the official docs recommend against it. 
See <a href="http://dev.mysql.com/doc/refman/5.5/en/password-security-user.html" rel="noreferrer">6.1.2.1 End-User Guidelines for Password Security (Mysql Manual for Version 5.6)</a>:
<blockquote>
Storing your password in the <code>MYSQL_PWD</code> environment variable
This method of specifying your MySQL password must be considered extremely insecure and should not be used. Some versions of ps include an option to display the environment of running processes. On some systems, if you set <code>MYSQL_PWD</code>, your password is exposed to any other user who runs ps. Even on systems without such a version of ps, it is unwise to assume that there are no other methods by which users can examine process environments.
</blockquote>

blocks|key|165380|text|另一种解决方案(例如，来自脚本)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|165381|+sed+-i''+-e+"s/password=.*\$/password=$pass/g"+~/.my.cnf
+mysql+-h+$host+-u+$user+$db_name+-e+"$sql_cmd"|code-block|syntax|javascript|165382|这里的-i''选项是为了与Mac兼容。标准UNIX+OSes可以直接使用-i|offset|length|style|CODE|165383|entityMap^0|0|0|3|4|10|2|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

Another solution (from a script, for example):

<pre><code> sed -i'' -e "s/password=.*\$/password=$pass/g" ~/.my.cnf
 mysql -h $host -u $user $db_name -e "$sql_cmd"
</code></pre>

The <code>-i''</code> option is here for compatibility with Mac OS X. Standard UNIX OSes can use straight <code>-i</code>

blocks|key|169173|text|您可以使用/dev/null执行mySQL并禁止显示警告和错误消息，例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|169174|#+if+you+run+just+a+SQL-command
mysql+-u+${USERNAME}+-p${PASSWORD}+-h+${HOST}+${DATABASE}+-e+"${STATEMENT}"+&>+/dev/null

#+Or+you+can+run+SQL-script+as+a+file
mysql+-u+${USERNAME}+-p${PASSWORD}+-h+${HOST}+${DATABASE}+<+${FILEPATH}+&>+/dev/null|code-block|syntax|javascript|169175|其中：|169176|${USERNAME}+-+existing+mysql+user

${PASSWORD}+-+password

${HOST}+++++-+ip+or+hostname,+for+example+'localhost'

${DATABASE}+-+name+of+database

${STATEMENT}-+SQL+command

${FILEPATH}+-+Path+to+the+SQL-script|169177|享受吧！|169178|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

You can execute mySQL and suppress warning and error messages by using /dev/null
for example:

<pre><code># if you run just a SQL-command
mysql -u ${USERNAME} -p${PASSWORD} -h ${HOST} ${DATABASE} -e "${STATEMENT}" &amp;&gt; /dev/null

# Or you can run SQL-script as a file
mysql -u ${USERNAME} -p${PASSWORD} -h ${HOST} ${DATABASE} &lt; ${FILEPATH} &amp;&gt; /dev/null
</code></pre>

Where:

<pre><code>${USERNAME} - existing mysql user

${PASSWORD} - password

${HOST} - ip or hostname, for example 'localhost'

${DATABASE} - name of database

${STATEMENT}- SQL command

${FILEPATH} - Path to the SQL-script
</code></pre>

enjoy!

blocks|key|2764310|text|shell>+mysql_config_editor+set+--login-path=local
+++++--host=localhost+--user=localuser+--password
Enter+password:+enter+password+"localpass"+here
shell>+mysql_config_editor+set+--login-path=remote
+++++--host=remote.example.com+--user=remoteuser+--password
Enter+password:+enter+password+"remotepass"+here|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2764311|要查看mysql_config_editor写入.mylogin.cnf文件的内容，请使用打印命令：|unstyled|2764312|shell>+mysql_config_editor+print+--all
[local]
user+=+localuser
password+=+*****
host+=+localhost
[remote]
user+=+remoteuser
password+=+*****
host+=+remote.example.com|2764313|print命令将每个登录路径显示为一组行，以方括号中表示登录路径名称的组头开头，后跟登录路径的选项值。密码值被屏蔽，不会以明文形式显示。|2764314|如前面的示例所示，.mylogin.cnf文件可以包含多个登录路径。通过这种方式，mysql_config_editor可以很容易地设置多个“个性”来连接到不同的MySQL服务器。当您调用客户机程序时，可以使用--login-path选项按名称选择其中的任何一个。例如，要连接到本地服务器，请使用以下命令：|2764315|shell>+mysql+--login-path=local|2764316|要连接到远程服务器，请使用以下命令：|2764317|shell>+mysql+--login-path=remote|2764318|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|V|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$B|C]]|$1|I|3|J|5|F|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$B|C]]|$1|O|3|P|5|F|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$B|C]]|$1|S|3|-4|5|F|7|12|8|@]|9|@]|A|$]]]|T|$]]

<pre><code>shell&gt; mysql_config_editor set --login-path=local
 --host=localhost --user=localuser --password
Enter password: enter password "localpass" here
shell&gt; mysql_config_editor set --login-path=remote
 --host=remote.example.com --user=remoteuser --password
Enter password: enter password "remotepass" here
</code></pre>

To see what mysql_config_editor wrote to the .mylogin.cnf file, use the print command:

<pre><code>shell&gt; mysql_config_editor print --all
[local]
user = localuser
password = *****
host = localhost
[remote]
user = remoteuser
password = *****
host = remote.example.com
</code></pre>

The print command displays each login path as a set of lines beginning with a group header indicating the login path name in square brackets, followed by the option values for the login path. Password values are masked and do not appear as clear text.

As shown by the preceding examples, the .mylogin.cnf file can contain multiple login paths. In this way, mysql_config_editor makes it easy to set up multiple “personalities” for connecting to different MySQL servers. Any of these can be selected by name later using the --login-path option when you invoke a client program. For example, to connect to the local server, use this command:

<pre><code>shell&gt; mysql --login-path=local
</code></pre>

To connect to the remote server, use this command:

<pre><code>shell&gt; mysql --login-path=remote
</code></pre>

blocks|key|165397|text|下面是我如何让我的每日mysqldump数据库备份的bash脚本更安全地工作。这是Cristian+Porta伟大的answer的扩展。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|165398|mysql+|165399|首先使用mysql_config_editor+(mysql+5.6%2B自带)设置加密的密码文件。假设你的用户名是"db_user“。从shell提示符运行：|unordered-list-item|style|BOLD|165400|165401|mysql_config_editor设置--登录路径=本地--主机=本地主机--用户=数据库用户--密码|165402|它会提示输入密码。输入后，用户/通行证将以加密方式保存在home/system_username/.mylogin.cnf中|CODE|165403|当然，在服务器上将"system_username“更改为您的用户名。|165404|165405|将您的bash脚本更改为：|ordered-list-item|165406|165407|mysqldump+-u+db_user+-pInsecurePassword+my_database+%7C+gzip+>+db_backup.tar.gz|165408|要这样做：|165409|db_backup.tar.gz+--login-path=local+my_database+%7C+gzip+>+mysqldump|165410|不再暴露密码。|165411|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/20854048/631764^0|1M|6|0|0|0|4|J|0|0|0|S|X|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1D|8|@]|9|@$A|1E|B|1F|1|1G]]|C|$]]|$1|D|3|E|5|6|7|1H|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1I|8|@$A|1J|B|1K|I|J]]|9|@]|C|$]]|$1|K|3|-4|5|6|7|1L|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|1M|8|@]|9|@]|C|$]]|$1|N|3|O|5|6|7|1N|8|@$A|1O|B|1P|I|P]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|S|3|-4|5|6|7|1R|8|@]|9|@]|C|$]]|$1|T|3|U|5|V|7|1S|8|@]|9|@]|C|$]]|$1|W|3|-4|5|6|7|1T|8|@]|9|@]|C|$]]|$1|X|3|Y|5|6|7|1U|8|@]|9|@]|C|$]]|$1|Z|3|10|5|6|7|1V|8|@]|9|@]|C|$]]|$1|11|3|12|5|6|7|1W|8|@]|9|@]|C|$]]|$1|13|3|14|5|6|7|1X|8|@]|9|@]|C|$]]|$1|15|3|-4|5|6|7|1Y|8|@]|9|@]|C|$]]]|16|$17|$5|18|19|1A|C|$1B|1C]]]]

Here's how I got my bash script for my daily mysqldump database backups to work more securely. This is an expansion of Cristian Porta's great <a href="https://stackoverflow.com/a/20854048/631764">answer</a>.
<ol>
<li>First use mysql_config_editor (comes with mysql 5.6+) to set up the encrypted password file. Suppose your username is &quot;db_user&quot;. Running from the shell prompt:
<pre><code> mysql_config_editor set --login-path=local --host=localhost --user=db_user --password
</code></pre>
It prompts for the password. Once you enter it, the user/pass are saved encrypted in your <code>home/system_username/.mylogin.cnf</code>
Of course, change &quot;system_username&quot; to your username on the server.
</li>
<li>Change your bash script from this:
<pre><code> mysqldump -u db_user -pInsecurePassword my_database | gzip &gt; db_backup.tar.gz
</code></pre>
to this:
<pre><code> mysqldump --login-path=local my_database | gzip &gt; db_backup.tar.gz
</code></pre>
</li>
</ol>
No more exposed passwords.

blocks|key|165417|text|就我个人而言，我使用脚本包装器来捕获该错误。以下是代码示例：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|165418|#!/bin/bash

#echo+$@+%7C+cat+>>+/home/mysqldump.log+2>/dev/null
ERR_FILE=/tmp/tmp_mdump.err

#+Execute+dumper
/usr/bin/mysqldump+$@+2>$ERR_FILE

#+Determine+error+and+remove+tmp+file
ERROR=`cat+$ERR_FILE`
rm+$ERR_FILE

#+Handle+an+error
if+[+""+!=+"$ERROR"+];+then

++++++++#+Error+occured
++++++++if+[+"Warning:+Using+a+password+on+the+command+line+interface+can+be+insecure."+!=+"$ERROR"+];+then
++++++++++++++++echo+$ERROR+>&2
++++++++++++++++exit+1
++++++++fi
fi|code-block|syntax|javascript|165419|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Personally, I use script wrapper to catch that error. Here is code sample:

<pre><code>#!/bin/bash

#echo $@ | cat &gt;&gt; /home/mysqldump.log 2&gt;/dev/null
ERR_FILE=/tmp/tmp_mdump.err

# Execute dumper
/usr/bin/mysqldump $@ 2&gt;$ERR_FILE

# Determine error and remove tmp file
ERROR=`cat $ERR_FILE`
rm $ERR_FILE

# Handle an error
if [ "" != "$ERROR" ]; then

 # Error occured
 if [ "Warning: Using a password on the command line interface can be insecure." != "$ERROR" ]; then
 echo $ERROR &gt;&amp;2
 exit 1
 fi
fi
</code></pre>

blocks|key|167508|text|来自https://gist.github.com/nestoru/4f684f206c399894952d|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|167509|#+Let+us+consider+the+following+typical+mysql+backup+script:
mysqldump+--routines+--no-data+-h+$mysqlHost+-P+$mysqlPort+-u+$mysqlUser+-p$mysqlPassword+$database

#+It+succeeds+but+stderr+will+get:
#+Warning:+Using+a+password+on+the+command+line+interface+can+be+insecure.
#+You+can+fix+this+with+the+below+hack:
credentialsFile=/mysql-credentials.cnf
echo+"[client]"+>+$credentialsFile
echo+"user=$mysqlUser"+>>+$credentialsFile
echo+"password=$mysqlPassword"+>>+$credentialsFile
echo+"host=$mysqlHost"+>>+$credentialsFile
mysqldump+--defaults-extra-file=$credentialsFile+--routines+--no-data+$database

#+This+should+not+be+IMO+an+error.+It+is+just+a+'considered+best+practice'
#+Read+more+from+http://thinkinginsoftware.blogspot.com/2015/10/solution-for-mysql-warning-using.html|code-block|syntax|javascript|167510|entityMap|0|LINK|mutability|MUTABLE|url|https://gist.github.com/nestoru/4f684f206c399894952d^0|2|1G|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

From <a href="https://gist.github.com/nestoru/4f684f206c399894952d" rel="noreferrer">https://gist.github.com/nestoru/4f684f206c399894952d</a>

<pre><code># Let us consider the following typical mysql backup script:
mysqldump --routines --no-data -h $mysqlHost -P $mysqlPort -u $mysqlUser -p$mysqlPassword $database

# It succeeds but stderr will get:
# Warning: Using a password on the command line interface can be insecure.
# You can fix this with the below hack:
credentialsFile=/mysql-credentials.cnf
echo "[client]" &gt; $credentialsFile
echo "user=$mysqlUser" &gt;&gt; $credentialsFile
echo "password=$mysqlPassword" &gt;&gt; $credentialsFile
echo "host=$mysqlHost" &gt;&gt; $credentialsFile
mysqldump --defaults-extra-file=$credentialsFile --routines --no-data $database

# This should not be IMO an error. It is just a 'considered best practice'
# Read more from http://thinkinginsoftware.blogspot.com/2015/10/solution-for-mysql-warning-using.html
</code></pre>

blocks|key|166531|text|如果您希望在命令行中使用密码，我发现这可以过滤出特定的错误消息：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|166532|mysqlcommand+2>&1+%7C+grep+-v+"Warning:+Using+a+password"|code-block|syntax|javascript|166533|它基本上是将标准错误重定向到标准输出，并使用grep删除与“警告:使用密码”匹配的所有行。|166534|这样，您就可以看到任何其他输出，包括错误。我将其用于各种shell脚本等。|166535|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

If you wish to use a password in the command line, I've found that this works for filtering out the specific error message:

<pre><code>mysqlcommand 2&gt;&amp;1 | grep -v "Warning: Using a password"
</code></pre>

It's basically redirecting standard error to standard output -- and using grep to drop all lines that match "Warning: Using a password".

This way, you can see any other output, including errors. I use this for various shell scripts, etc.

blocks|key|2977319|text|我遇到的问题是在bash脚本中使用条件输出。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2977320|这并不优雅，但在docker环境中，这真的无关紧要。基本上，所有这些操作都是忽略不在最后一行的输出。您可以使用awk执行类似的操作，并更改为返回除第一行以外的所有内容。|2977321|这只返回最后一行|2977322|mysql+-u+db_user+-pInsecurePassword+my_database+...+%7C+sed+-e+'$!d'|code-block|syntax|javascript|2977323|它不会抑制错误，但会确保您可以在bash脚本中使用查询的输出。|2977324|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|R|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

The problem I had was using the output in a conditional in a bash script.

This is not elegant, but in a docker env this should really not matter.
Basically all this does is ignore the output that isn't on the last line. 
You can do similar with awk, and change to return all but the first line etc. 

This only returns the Last line

<pre><code>mysql -u db_user -pInsecurePassword my_database ... | sed -e '$!d'
</code></pre>

It won't suppress the error, but it will make sure you can use the output of a query in a bash script.

blocks|key|166549|text|一个简单的变通脚本。将其命名为"mysql"，并将其放在路径中"/usr/bin“之前。其他命令的明显变体，或者警告文本不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|166550|#!/bin/sh

(
(
(
(
(
++++/usr/bin/mysql+"$@"
)+1>&9+
)+2>&1
)+%7C+fgrep+-v+'mysql:+[Warning]+Using+a+password+on+the+command+line+interface+can+be+insecure.'
)+1>&2+
)+9>&1|code-block|syntax|javascript|166551|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

A simple workaroud script. Name this "mysql", and put it in your path before "/usr/bin". Obvious variants for other commands, or if the warning text is different.

<pre><code>#!/bin/sh

(
(
(
(
(
 /usr/bin/mysql "$@"
) 1&gt;&amp;9 
) 2&gt;&amp;1
) | fgrep -v 'mysql: [Warning] Using a password on the command line interface can be insecure.'
) 1&gt;&amp;2 
) 9&gt;&amp;1
</code></pre>

blocks|key|2764417|text|它对我很有效--只是在$(mysql_command)之后添加了2>+null，而且它只会抑制错误和警告消息。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2764418|entityMap^0|B|G|W|7|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

It worked for me-
Just added <code>2&gt; null</code> after the <code>$(mysql_command)</code>, and it will suppress the Errors and Warning messages only.

blocks|key|167577|text|以下是Docker在脚本/bin/sh中的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|167578|根docker+exec+MYSQL_CONTAINER_NAME+sh+-c+'exec+echo+"client“>/+|167579|+/mysql-redentials.cnf‘|blockquote|167580|167581|docker+exec根sh+-c+'exec+echo+"user=root“>>+/>>/mysql-echo‘|167582|docker+exec根sh+-c+'exec+echo+"password=$MYSQL_ROOT_PASSWORD“>>+/>>/mysql-echo‘|167583|docker+exec+--defaults-extra-file=/root/mysql-credentials.cnf+sh+-c+'exec+mysqldump+docker--+MYSQL_CONTAINER_NAME+--c‘|167584|167585|替换MYSQL_CONTAINER_NAME，并确保在容器中设置了环境变量MYSQL_ROOT_PASSWORD。|167586|希望它能帮助你，就像它能帮助我一样！|167587|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|10|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

Here is a solution for Docker in a script /bin/sh :
<blockquote>
docker exec [MYSQL_CONTAINER_NAME] sh -c 'exec echo &quot;[client]&quot; &gt; /root/mysql-credentials.cnf'
docker exec [MYSQL_CONTAINER_NAME] sh -c 'exec echo &quot;user=root&quot; &gt;&gt; /root/mysql-credentials.cnf'
docker exec [MYSQL_CONTAINER_NAME] sh -c 'exec echo &quot;password=$MYSQL_ROOT_PASSWORD&quot; &gt;&gt; /root/mysql-credentials.cnf'
docker exec [MYSQL_CONTAINER_NAME] sh -c 'exec mysqldump --defaults-extra-file=/root/mysql-credentials.cnf --all-databases'
</blockquote>
Replace [MYSQL_CONTAINER_NAME] and be sure that the environment variable MYSQL_ROOT_PASSWORD is set in your container.
Hope it will help you like it could help me !

blocks|key|2977426|text|对于PowerShell+(pwsh，而不是bash)来说，这是一个相当粗糙的解决方案……我的第一个尝试是将对mysql的调用包装在一个try/catch函数中，但是由于一些strange+behavior+in+PowerShell+error+handling，这是不可行的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2977427|解决方案是覆盖$ErrorActionPreference，只需足够长的时间来组合和捕获STDERR和STDOUT，并解析单词ERROR并根据需要重新抛出。我们不能在"%5Emysql.*Warning.*password"上捕获和释放的原因是因为PowerShell将错误作为一个流来处理和引发，所以你的必须捕获所有的以便过滤和重新抛出。:/|BOLD|2977428|Function+CallMySQL()+{
++++#+Cache+the+error+action+preference
++++$_temp+=+$ErrorActionPreference
++++$ErrorActionPreference+=+"Continue"

++++#+Capture+all+output+from+mysql
++++$output+=+(&mysql+--user=foo+--password=bar+2>&1)

++++#+Restore+the+error+action+preference
++++$ErrorActionPreference+=+$_temp

++++if+($output+-match+"ERROR")+{
++++++++throw+$output
++++}+elseif($output)+{
++++++++"+++Swallowing+$output"
++++}+else+{
++++++++"+++No+output"
++++}
}|code-block|syntax|javascript|2977429|注意：+PowerShell可用于Unix，因此此解决方案是跨平台的。它可以通过一些微小的语法修改来适应bash。|2977430|+warning+:有几十种不起作用的边缘情况，例如非英语错误消息或在输出中任意位置返回单词ERROR的语句，但它足以在不破坏整个脚本的情况下接受对mysql的基本调用的警告。希望其他人会发现这一点很有用。|2977431|如果mysql只是简单地添加一个选项来抑制此警告，那就太好了。|2977432|entityMap|0|LINK|mutability|MUTABLE|url|https://mathieubuisson.github.io/erroractionpreference-try-catch/^0|E|4|M|4|1J|5|1W|9|2F|19|0|0|7|M|18|6|1F|6|1R|5|2B|R|47|7|0|0|0|3|1G|4|0|0|A|1A|5|22|5|0|2|5|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]|$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@$9|1A|A|1B|1|1C]]|E|$]]|$1|F|3|G|5|6|7|1D|8|@$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]|$9|1K|A|1L|B|C]|$9|1M|A|1N|B|C]|$9|1O|A|1P|B|H]]|D|@]|E|$]]|$1|I|3|J|5|K|7|1Q|8|@]|D|@]|E|$L|M]]|$1|N|3|O|5|6|7|1R|8|@$9|1S|A|1T|B|H]|$9|1U|A|1V|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1W|8|@$9|1X|A|1Y|B|H]|$9|1Z|A|20|B|C]|$9|21|A|22|B|C]]|D|@]|E|$]]|$1|R|3|S|5|6|7|23|8|@$9|24|A|25|B|C]]|D|@]|E|$]]|$1|T|3|-4|5|6|7|26|8|@]|D|@]|E|$]]]|U|$V|$5|W|X|Y|E|$Z|10]]]]

For PowerShell (<code>pwsh</code>, not <code>bash</code>), this was quite a rube-goldberg solution... My first attempt was to wrap the calls to <code>mysql</code> in a <code>try/catch</code> function, but due to some <a href="https://mathieubuisson.github.io/erroractionpreference-try-catch/" rel="nofollow noreferrer">strange behavior in PowerShell error handling</a>, this wasn't viable.

The solution was to override the <code>$ErrorActionPreference</code> just long enough to combine and capture <code>STDERR</code> and <code>STDOUT</code> and parse for the word <code>ERROR</code> and re-throw as needed. The reason we couldn't catch and release on <code>"^mysql.*Warning.*password"</code> is because PowerShell handles and raises the error as one stream, so you must capture it all in order to filter and re-throw. :/

<pre><code>Function CallMySQL() {
 # Cache the error action preference
 $_temp = $ErrorActionPreference
 $ErrorActionPreference = "Continue"

 # Capture all output from mysql
 $output = (&amp;mysql --user=foo --password=bar 2&gt;&amp;1)

 # Restore the error action preference
 $ErrorActionPreference = $_temp

 if ($output -match "ERROR") {
 throw $output
 } elseif($output) {
 " Swallowing $output"
 } else {
 " No output"
 }
}
</code></pre>

Note: PowerShell is available for Unix, so this solution is cross-platform. It can be adapted to <code>bash</code> with some minor syntax modifications.

Warning: There are dozens of edge-cases where this won't work such as non-english error messages or statements that return the word <code>ERROR</code> anywhere in the output, but it was enough to swallow the warning for a basic call to <code>mysql</code> without bombing out the entire script. Hopefully others find this useful.

It would be nice if <code>mysql</code> simply added an option to suppress this warning.

blocks|key|165512|text|也可以将标准错误STDERR输出重定向到/dev/null|type|unstyled|depth|inlineStyleRanges|entityRanges|data|165513|所以就这么做吧：|165514|mysql+-u+$user+-p$password+-e+"statement"+2>+/dev/null|offset|length|style|CODE|165515|entityMap^0|0|0|0|1I|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@$F|O|G|P|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

You can also just redirect the standard error STDERR output to /dev/null

So just do:

<code>mysql -u $user -p$password -e "statement" 2&gt; /dev/null</code>

blocks|key|169341|text|最好的解决方案是使用别名：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|169342|alias+[yourapp]-mysql="mysql+-u+root+-psomepassword+-P3306+-h+127.0.0.1"|code-block|syntax|javascript|169343|例如，将以下内容放入脚本中：|169344|alias+drupal-mysql="mysql+-u+root+-psomepassword+-P3306+-h+127.0.0.1"|169345|然后在脚本中加载数据库：|169346|drupal-mysql+database_name+<+database_dump.sql|169347|要运行语句，请执行以下操作：|169348|drupal-mysql+-e+"EXEC+SOMESTATEMENT;"|169349|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

the best solution is to use alias:

<pre><code>alias [yourapp]-mysql="mysql -u root -psomepassword -P3306 -h 127.0.0.1"
</code></pre>

example, put this in your script:

<pre><code>alias drupal-mysql="mysql -u root -psomepassword -P3306 -h 127.0.0.1"
</code></pre>

then later in your script to load a database:

<pre><code>drupal-mysql database_name &lt; database_dump.sql
</code></pre>

to run a statement:

<pre><code>drupal-mysql -e "EXEC SOMESTATEMENT;"
</code></pre>

blocks|key|169351|text|好的，没有临时文件或任何东西的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|169352|mysql+--defaults-extra-file=<(echo+$'[client]\npassword='"$password")+-u+$user+-e+"statement"|code-block|syntax|javascript|169353|它与其他人提到的类似，但是这里您不需要实际的文件，命令的这一部分伪造文件：<(echo+...)+<(+(请注意，<(echo+...)中间没有空格|offset|length|style|CODE|BOLD|169354|entityMap^0|0|0|11|B|1D|2|1L|B|1D|2|1W|6|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Q|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|R|8|@$I|S|J|T|K|L]|$I|U|J|V|K|L]|$I|W|J|X|K|L]|$I|Y|J|Z|K|M]|$I|10|J|11|K|M]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|O|$]]

ok, solution without temporary files or anything:

<pre><code>mysql --defaults-extra-file=&lt;(echo $'[client]\npassword='"$password") -u $user -e "statement"
</code></pre>

it is similar to what others have mentioned, but here you don't need an actual file, this part of the command fakes the file: <code>&lt;(echo ...)</code> (notice there is no space in the middle of <code>&lt;(</code>

blocks|key|2977493|text|最简单的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2977494|mysql+-u+root+-p+YOUR_DATABASE|code-block|syntax|javascript|2977495|输入这个，你需要输入你的密码。|2977496|注:是的，不带分号。|2977497|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

The easiest way:

<pre><code>mysql -u root -p YOUR_DATABASE
</code></pre>

Enter this and you'll need to type your password in. 

Note: Yes, without a semicolon.

blocks|key|2764560|text|定义辅助对象：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2764561|remove-warning+()+{
++++grep+-v+'mysql:+[Warning]+Using+a+password+on+the+command+line+interface+can+be+insecure.'
}|code-block|syntax|javascript|2764562|使用它：|2764563|mysql+-u+$user+-p$password+-e+"statement"+2>&1+%7C+remove-warning|2764564|塔坎！你的代码很干净，读起来也很好。|2764565|(使用bash测试)|2764566|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Define the helper:

<pre><code>remove-warning () {
 grep -v 'mysql: [Warning] Using a password on the command line interface can be insecure.'
}
</code></pre>

Use it:

<pre><code>mysql -u $user -p$password -e "statement" 2&gt;&amp;1 | remove-warning
</code></pre>

Tachaan! Your code is clean and nice to read

(tested with bash)

blocks|key|165609|text|如果您碰巧使用Rundeck来调度您的任务，或者您请求mylogin.cnf文件的任何其他平台，我已经成功地使用以下shell代码在继续执行sql调用之前为该文件提供了一个新位置：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|165610|if+test+-f+"$CUSTOM_MY_LOGINS_FILE_PATH";+then
+++chmod+600+$CUSTOM_MY_LOGINS_FILE_PATH
+++export+MYSQL_TEST_LOGIN_FILE="$CUSTOM_MY_LOGINS_FILE_PATH"
fi

...

result=$(mysql+--login-path=production+-NBA+-D+$schema+-e+"$query")|code-block|syntax|javascript|165611|其中MYSQL_TEST_LOGIN_FILE是一个环境变量，可以将其设置为与默认文件路径不同的文件路径。|165612|如果您在派生进程中运行，并且不能将文件移动或复制到$HOME目录中，这将特别有用。|165613|See+documentation+here.|165614|entityMap|0|LINK|mutability|MUTABLE|url|https://dev.mysql.com/doc/refman/5.6/en/mysql-config-editor.html^0|R|B|0|0|2|L|0|P|5|0|0|N|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|18|8|@]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|Q|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

If you happen to use Rundeck for scheduling your tasks, or any other platform where you ask for a <code>mylogin.cnf</code> file, I have successfully used the following shell code to provide a new location for the file before proceeding with sql calls:

<pre><code>if test -f "$CUSTOM_MY_LOGINS_FILE_PATH"; then
 chmod 600 $CUSTOM_MY_LOGINS_FILE_PATH
 export MYSQL_TEST_LOGIN_FILE="$CUSTOM_MY_LOGINS_FILE_PATH"
fi

...

result=$(mysql --login-path=production -NBA -D $schema -e "$query")
</code></pre>

Where <code>MYSQL_TEST_LOGIN_FILE</code> is an environment variable that can be set to a different file path than the default one.

This is especially useful if you are running in a forked process and can't move or copy files to the <code>$HOME</code> directory.

<a href="https://dev.mysql.com/doc/refman/5.6/en/mysql-config-editor.html" rel="nofollow noreferrer">See documentation here.</a>

blocks|key|2977575|text|这很简单。这是我的工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2977576|export+MYSQL_PWD=password;+mysql+--user=username+-e+"statement"|code-block|syntax|javascript|2977577|MYSQL_PWD是environment+variables+that+are+used+directly+or+indirectly+by+MySQL中的一员。|offset|length|style|CODE|2977578|从文档中：|2977579|2977580|+MYSQL_PWD+-连接到mysqld时的默认密码。使用它是不安全的。参见Section+6.1.2.1,+“End-User+Guidelines+for+Password+Security”。|blockquote|2977581|2977582|entityMap|0|LINK|mutability|MUTABLE|url|https://dev.mysql.com/doc/refman/5.6/en/environment-variables.html|1|https://dev.mysql.com/doc/refman/5.6/en/password-security-user.html^0|0|0|0|9|A|1V|0|0|0|0|13|1O|1|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|14|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|15|8|@$I|16|J|17|K|L]]|9|@$I|18|J|19|1|1A]]|A|$]]|$1|M|3|N|5|6|7|1B|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1D|8|@]|9|@$I|1E|J|1F|1|1G]]|A|$]]|$1|S|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]|11|$5|W|X|Y|A|$Z|12]]]]

It's very simple. This is work for me.
<pre><code>export MYSQL_PWD=password; mysql --user=username -e &quot;statement&quot;
</code></pre>
<code>MYSQL_PWD</code> is one of the <a href="https://dev.mysql.com/doc/refman/5.6/en/environment-variables.html" rel="nofollow noreferrer">environment variables that are used directly or indirectly by MySQL</a>.
From the docs:
<blockquote>
MYSQL_PWD - The default password when connecting to mysqld. Using this is insecure. See <a href="https://dev.mysql.com/doc/refman/5.6/en/password-security-user.html" rel="nofollow noreferrer">Section 6.1.2.1, “End-User Guidelines for Password Security”</a>.
</blockquote>

blocks|key|169417|text|@david-g的答案非常好，但至少BSD+grep会将[Warning]解释为单个字符的正则表达式表示(匹配单词Warning中的任何一个字符)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|169418|对于我的脚本，我使用了相同的方法，封装在一个函数中(为了简单起见，只匹配字符串的一部分)：|169419|mysql()+{
++(
++++(
++++++(
++++++++(
++++++++++(
++++++++++++/usr/local/bin/mysql+"$@"
++++++++++)+1>&9
++++++++)+2>&1
++++++)+%7C+grep+-v+'Using+a+password+on+the+command+line+interface+can+be+insecure.'
++++)+1>&2
++)+9>&1
}

out=$(mysql+......+2>&1)
rc=$?|code-block|syntax|javascript|169420|上面的代码将使用一组选项调用mysql，将过滤后的stderr重定向到stdout，并捕获$opt中的组合输出和$rc中的退出代码。|169421|entityMap^0|M|4|S|9|1L|7|0|0|0|19|4|1K|3|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|P|$]]

The answer from @david-g is quite excellent, but at least BSD <code>grep</code> will interpret the <code>[Warning]</code> as a regular expression representation of a single character (matching any one of the characters in the word <code>Warning</code>).
For my scripts, I'm using the same approach, wrapped in a function (and only matching parts of the string, for simplicity):
<pre class="lang-sh prettyprint-override"><code>mysql() {
 (
 (
 (
 (
 (
 /usr/local/bin/mysql &quot;$@&quot;
 ) 1&gt;&amp;9
 ) 2&gt;&amp;1
 ) | grep -v 'Using a password on the command line interface can be insecure.'
 ) 1&gt;&amp;2
 ) 9&gt;&amp;1
}

out=$(mysql ...... 2&gt;&amp;1)
rc=$?
</code></pre>
The above will call mysql with a set of options, redirect the filtered stderr to stdout, and capture the combined output in <code>$opt</code> and the exit code in <code>$rc</code>.

When I tried running the following command on MySQL from within Terminal:

<pre><code>mysql -u $user -p$password -e "statement"
</code></pre>

The execution works as expected, but it always issues a warning:

<blockquote>
 Warning: Using a password on the command line interface can be insecure. 
</blockquote>

However, I have to conduct the statement above using an environment variable (<code>$password</code>) that stores my password, because I want to run the command iteratively in bash script from within Terminal, and I definitely don't like the idea of waiting a prompt showing up and forcing me to input my password 50 or 100 times in a single script. So here's my question:

<ul>
<li>Is it feasible to suppress the warning? The command works properly as I stated, but the window becomes pretty messy when I loop over and run the command 50 or 100 times.</li>
<li>Should I obey the warning message and do NOT write my password in my script? If that's the case, then do I have to type in my password every time the prompt forces me to do so?</li>
</ul>

Running <code>man mysql</code> doesn't help, saying only 

<blockquote>
 <code>--show-warnings</code> 
 Cause warnings to be shown after each statement if there are any. This option applies to interactive and batch mode.
</blockquote>

and mentions nothing about how to turn off the functionality, if I'm not missing something.

I'm on OS X 10.9.1 Mavericks and use MySQL 5.6 from homebrew.

Suppress warning messages using mysql from within Terminal, but password written in bash script

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

当我尝试从终端内在MySQL上运行以下命令时：mysql -u $user -p$password -e "statement"执行按预期工作，但它总是发出警告：警告:在命令行界面上使用密码可能不安全。但是，我必须使用存储密码的环境变量($password)来执行上面的语句，因为我希望在终端内的bash脚本中迭代地运行...

问禁止在终端内使用mysql显示警告消息，但使用bash脚本编写密码
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问禁止在终端内使用mysql显示警告消息，但使用bash脚本编写密码EN