| Summary: | Packaging: mysql-server logfile is marked as a "configuration file" | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | David Tonhofer <bughunt> |
| Component: | mysql | Assignee: | Michal Schorm <mschorm> |
| Status: | CLOSED WONTFIX | QA Contact: | qe-baseos-daemons |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1 | CC: | byte, databases-maint, hhorak, praiskup, psklenar |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-07 19:18:04 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 947775, 1070830, 1159820 | ||
|
Description
David Tonhofer
2011-10-31 01:55:30 UTC
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. It's not apparent to me exactly what you think the problem is? mysqld.log is supposed to be marked that way, per advice going back to bug #102190. Unfortunately, "You are not authorized to access bug #102190" The problem is that you get a package verification warning when the log file is missing - which happens because MySQL may have been configured to log some other file, this is the case on our installations for example. After all, it's just a logfile. Compare with httpd or syslog - No complains on "missing logfiles" here. Best regards, -- David Well, the file is created by installing the RPM, so the only way you'd get such a message is if you manually removed the file ... and I see nothing particularly wrong with that. Is this why I sometimes have a file "/var/log/mysqld.log.rpmnew" after a yum update? This file is always empty. Other log files do not do this. The existence of the rpmnew file creates maintenance overhead for me as I need to analyze if any change in a _config_ is required. (In this case it should simply be deleted.) There is quite good summary of the log files issue at: http://fedoraproject.org/wiki/PackagingDrafts/Logfiles And since the mysqld log file should be owned by mysql user, the following seems like a best we can do (now used in Fedora): %attr(0640,mysql,mysql) %config %ghost %verify(not md5 size mtime) /var/log/mysqld.log |