https://bugzilla.novell.com/show_bug.cgi?id=635645 https://bugzilla.novell.com/show_bug.cgi?id=635645#c0 Summary: mysql init script fails to start when SELinux is enabled Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ldav1s@yahoo.com QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=386326) --> (http://bugzilla.novell.com/attachment.cgi?id=386326) fixed startup issue on SELinux enabled installation After I enabled SELinux, I was unable to start mysql: # /etc/init.d/mysql start Can't create secure /var/tmp/mysql.QyEda9 It turns out that I was unable to start the script because GNU ls behaves slightly differently when SELinux is enabled and files/directories have security contexts. According to the documentation at http://www.gnu.org/software/coreutils/manual/coreutils.html#ls-invocation: Following the file mode bits is a single character that specifies whether an alternate access method such as an access control list applies to the file. When the character following the file mode bits is a space, there is no alternate access method. When it is a printing character, then there is such a method. GNU ls uses a ‘.’ character to indicate a file with an SELinux security context, but no other alternate access method. A file with any other combination of alternate access methods is marked with a ‘+’ character. So I made some adjustments to grep regular expressions in the attached patch to look for '.' or '+' in some 'ls -ld' pipelines and mysql started up OK. I have not tried the patch on an non-SELinux enabled box to make sure it isn't broken there. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.