You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2018. It is now read-only.
Why was the calling of /usr/bin/mysqld_safe changed?
- /usr/bin/mysqld_safe > /dev/null 2>&1 &
+ su - mysql -s /bin/sh -c "/usr/bin/mysqld_safe > /dev/null 2>&1 &"
Is there are a reason for this? This is the reason why the settings from my.cnf can't be used. The ulimit in mysqld_safe will be only executed if the current user is root.
Will this be fixed to the old behaviour? Otherwise thousands of installations have to change their /etc/security/limits.confand/etc/pam.d/su because the later file don't use "pam_limits.so". It's out commented.
out of the box after an upgrade from debian stock mysql 5.5 to dotdeb 5.6 gives me the following error in daemon.log
Buffered warning: Could not increase number of max_open_files
i tried setting my /etc/security/limits.conf but to no avail
any ideas?
The text was updated successfully, but these errors were encountered: