databases/mysql57-server should remind the user of the autogenerated, random root password stored in ~/.mysql_secret, which is generated upon bootstrapping MySQL 5.7. pkg-message is a good candidate.
(In reply to Trond.Endrestol from comment #0)
Hi thanks for your feedback :)
I've solve this by a patch, just waiting to be committed :D
Fixed in r408005 via patch provided in bug 205956.
MFH into 2016Q1 requested in r408005.
A commit references this bug:
Date: Thu Feb 4 06:16:30 UTC 2016
New revision: 408012
- Fix plist
- binary_log_types.h is now installed only by client, not server
- lib/mysql/plugin/ha_example.so is only installed if
EXAMPLES OPTION is turned off
- Bump PORTREVISION
- Allow slave port to override PORTREVISION if necessary
- Deactivate performance_schema feature to conserve memory
- Add notes to pkg-message:
- root password
- performance_schema feature is deactivated by default to reduce
- Allow port to build while boost-libs-1.55 is installed
PR: 205956 206065 206612 206879
Submitted by: smh
Reviewed by: firstname.lastname@example.org (maintainer)
Approved by: ports-secteam (feld), email@example.com (maintainer)
Created attachment 174385 [details]
Show autogenerated password WHEN it is created.
I don't consider the pkg-message fix a good solution. Firstly, it assumes the installer is the same as the user starting MySQL or communicating (not the default case in a hosting/user relationship). Secondly, I completely missed this, as pkg(8) groups all package messages, and this one had scrolled out of my terminal history when installing a fresh jail with a large set of tools. And thirdly, all package messages are always shown by pkg(8) creating message blindness (this is out of the scope of this bug but should be considered when breaking a long standing practice).
The fix in the patch shows the password when the command is run and also does not use the deprecated mysql_install_db command anymore. Since this output is very limited and it's much more likely the attention of the user is at the screen at that time, this has less chances of failing.
And last but not least:
$USER may have privileges to run `sudo service mysql-server start`, but not `sudo cat /root/.mysql_secret` making the file useless.
Can this report be re-opened or shall I create a new one?