If a query was ignored on the slave (because of
            replicate-ignore-table and other similar
            rules), the slave still checked if the query got the same
            error code (0, no error) as on the master. So if the master
            had an error on the query (for example, ``Duplicate entry''
            in a multiple-row insert), then the slave stopped and warned
            that the error codes didn't match. This is a backport of the
            fix for MySQL 4.0. (Bug#797)
          
            mysqlbinlog now asks for a password at
            console when the -p/--password option is
            used with no argument. This is how the other clients
            (mysqladmin,
            mysqldump..) already behave. Note that
            one now has to use mysqlbinlog
            -p<my_password>; mysqlbinlog -p
            <my_password> will not work anymore (in
            other words, put no space after -p). (Bug#1595)
          
On some 64-bit machines (some HP-UX and Solaris machines), a slave installed with the 64-bit MySQL binary could not connect to its master (it connected to itself instead). (Bug#1256, #1381)
            Fixed a Windows-specific bug present since MySQL version
            3.23.57 and 3.23.58, which caused Windows slaves to crash
            when they started replication if a
            master.info file existed. (Bug#1720)
          
This is a translation of the MySQL Reference Manual that can be found at dev.mysql.com. The original Reference Manual is in English, and this translation is not necessarily as up to date as the English version.

