[MDEV-7393] Setting log-basename in my.cnf will ignore pid-file and log-error settings Created: 2014-12-29  Updated: 2022-11-19  Resolved: 2022-11-19

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.0.15
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Brian Evans Assignee: Michael Widenius
Resolution: Fixed Votes: 0
Labels: None
Environment:

Gentoo


 Description   

Simply by adding "log-basename = master" to a my.cnf file, the definitions for pid-file and log-error are ignored.

This may include other settings as well but I cannot confirm that.

How to repeat:

my.cnf

 
pid-file=/var/run/mysqld/mysqld.pid
 
log-error=/var/log/mysql/mysqld.err
 
log-basename = master

Expected results:
/var/run/mysqld/mysqld.pid and /var/log/mysql/mysqld.err to be written to.

Actual results:
$DATADIR/master.pid and $DATADIR/master.err are created and written to

 Comments   
Comment by Brian Evans [ 2014-12-29 ]

putting log-basename first works as expected

Comment by Elena Stepanova [ 2014-12-30 ]

I think it's natural behavior, consistent with how server options are treated in general. You have one option that sets the value for a variable, then you have another one that contradicts the first one, so the first one gets ignored and the later one is used.

Assigning to monty (as the author of the option) to confirm.

Comment by Sergei Golubchik [ 2022-11-19 ]

it seems that now (from commit 9cba6c5aa3b15f, first in 10.2.27) log-basename only updates pid-file if it wasn't set explicitly before. It still updates log-error even if it was set before, but not if it was disabled.

Generated at Thu Feb 08 07:19:15 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.