problems upgrading mysql 5.6 => 5.7

John Levine johnl at iecc.com
Sun Mar 21 23:58:54 UTC 2021


It appears that Gary Aitken <freebsd at dreamchaser.org> said:
>$ cat ~/.my.cnf:
>[mysqld]
>datadir=/hd2/home/me/mysql_data
>tmpdir=/hd2/home/me/tmp
>innodb_strict_mode=on
>
>The data directory is writable by the user starting mysqld, as are all of the files in it:
>
>$ ls -l
>-rw-------  1 me  me        56 Oct 15  2016 auto.cnf
>-rw-r-----  1 me  me     10040 Mar 21 12:47 breakaway.dreamchaser.org.err
>-rw-------  1 me  me         5 Jan  7  2020 breakaway.pid
>-rw-------  1 me  me  50331648 Feb  6  2020 ib_logfile0
>-rw-------  1 me  me  50331648 Oct 15  2016 ib_logfile1
>-rw-------  1 me  me  27262976 Feb  6  2020 ibdata1
>drwx------  2 me  me      2560 Oct 15  2016 mysql
>-rw-------  1 me  me         0 Feb  8  2020 mysql-bin.index
>-rw-------  1 me  me         6 Oct 15  2016 mysql_upgrade_info
>drwx------  2 me  me      2560 Oct 15  2016 performance_schema
>
>The system directory /var/db/mysqld exists and is owned/writeable by the mysql user, as are all of the files in it.

If you're using the mysql-server package, Mysql runs as the mysql
user, user ID 88, and all of its data files should belong
to mysql.

Unless you really REALLY know what you are doing, nothing but mysql should be
writing the files in its database directory so nobody else should have write access to it.




More information about the freebsd-questions mailing list