Bug 14863 - mysqld_safe is required for backwards compatibility
Summary: mysqld_safe is required for backwards compatibility
Status: CLOSED FIXED
Alias: None
Product: Sisyphus
Classification: Development
Component: MySQL-server (show other bugs)
Version: unstable
Hardware: all Linux
: P2 normal
Assignee: Anton Farygin
QA Contact: qa-sisyphus
URL: http://lists.altlinux.org/pipermail/s...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-11 21:51 MSK by Dmitry V. Levin
Modified: 2008-03-16 15:00 MSK (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry V. Levin 2008-03-11 21:51:46 MSK
http://dev.mysql.com/doc/refman/4.1/en/mysqld-safe.html

"Before MySQL 4.0, mysqld_safe is named safe_mysqld. To preserve backward
compatibility, MySQL binary distributions include safe_mysqld as a
symbolic link to mysqld_safe until MySQL 5.1."

http://dev.mysql.com/doc/refman/5.0/en/mysqld-safe.html

"To preserve backward compatibility with older versions of MySQL, MySQL
binary distributions still include safe_mysqld as a symbolic link to
mysqld_safe. However, you should not rely on this because it is removed
as of MySQL 5.1."
Comment 1 Konstantin A Lepikhov (L.A. Kostis) 2008-03-16 15:00:10 MSK
Fixed in MySQL-5.0.51-alt2.a