Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 19582

Summary:	/var/log/mysqld.log is query log, not error log
Product:	[Retired] Red Hat Linux	Reporter:	Morgan Christiansson <mog>
Component:	mysql	Assignee:	Patrick Macdonald <patrickm>
Status:	CLOSED RAWHIDE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	dr
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-10-23 03:35:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Morgan Christiansson 2000-10-23 03:35:34 UTC

change --log=/var/log/mysqld.log to --err-log=/var/log/mysqld.log in
/etc/rc.d/init.d/mysqld to make /var/log/mysqld.log an error log instead of
a query log.

Comment 1 Trond Eivind Glomsrxd 2000-10-23 16:36:21 UTC

Fixed in 26-2. Thanks.

Comment 2 Trond Eivind Glomsrxd 2000-10-23 19:02:48 UTC

Reverted. Mysql doesn't seem to support this - take a look at the options from
/usr/libexec/mysqld

Comment 3 Morgan Christiansson 2000-10-23 21:14:52 UTC

It seems like safe_mysqld script supports --err-log but when starting the mysqld
daemon it also passess $@ as arguments, which is all arguments to the
safe_mysqld script

the mysqld daemon does not support the --err-log option and therefore an error
is generated.

Suggested fix:
on line 46 in /usr/bin/safe_mysqld, change
err_log=$DATADIR/`/bin/hostname`.err
to
err_log=/var/log/mysqld.log


i think this is the easiest way to fix this without messing around with the
script too much

or using the my_print_defaults program but it doesn't seem to work as it should
from the safe_mysqld script


seems kinda messy that safe_mysqld script, dont ya think?

maybe a cleaner reinplementation of it in the /etc/rc.d/init.d/mysqld script
would be nice? or just a cleanup

but on the other hand this might be the work of the mysql development team?