Re: mariadb need additional cmake options to fit the mariadb user and group

"Zhang Wen" ([email protected] via blfs-dev Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.beyond.devel
Message-ID <[email protected]>
On 1/25/25 04:11, "Douglas R. Reno" ([email protected] via 
blfs-dev Mailing List) wrote:
> On 1/24/25 6:49 AM, Zhang Wen ([email protected] via blfs-dev Mailing 
> List) wrote:
>> We changed username used by mariadb from mysql to mariadb on 11.4.3 
>> update, but the mariadbd-safe script is still using mysql user, which 
>> is causing issues trying to reset the root password of mariadb.
>> This is controled by the MYSQLD_USER and MYSQLD_GROUP cmake options.
>>
> Hi Zhang,
> 
> I tried to reproduce this and couldn't unfortunately. The book currently 
> has: "mariadbd-safe --user=mariadb 2>&1 >/dev/null &" as the command to 
> start the MariaDB server, which matches with the mariadb user that we 
> created earlier on the page. I was able to use the commands in the book 
> currently to setup a new database and then change the password for it!
> 
> Can you verify that the commands that you're using match what is in the 
> book, and verify your configuration?
> 
> Thank you,
> 
> - Doug
> 
> 
Back to the times when we are using mysql, if we forgot the root user 
password, the typically solution is to start the database daemon with 
mysql_safe command and login to mysql, then set the root password again. 
I tried to do the same thing for mariadb since it's a continue of mysql, 
but this time it didn't work because the mariadbd-safe command is 
looking for the mysql user.
If we compile mariadb with the two options i mentioned, then the users 
following the old blogs to reset the root password of database can start 
mariadb daemon with the single mariadb-safe command. I can't see what 
else will this change hurt.

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.