MySQL Bugs: #3204: "mysqlbinlog --read-from-remote-server this

Bug #3204	"mysqlbinlog --read-from-remote-server this_binlog.001" prints all binlogs
Submitted:	17 Mar 2004 9:48	Modified:	18 Mar 2004 9:34
Reporter:	Guilhem Bichot	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	4.0	OS:	Any (all)
Assigned to:	Guilhem Bichot	CPU Architecture:	Any

Description:
if I do
mysqlbinlog aa-bin.001
I get aa-bin.001. If I do
mysqlbinlog --read-from-remote-server aa-bin.001
I get aa-bin.001 then aa-bin.002 etc until the end of the binlogs.
I would expect to get only aa-bin.001,
and to get the others only if I requested them on the command line,
like it works when reading local logs. To be consistent.

How to repeat:
see description.

Suggested fix:
will work on it.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

This is fixed in the 4.1 tree, as it is a behaviour change (even though the previous behaviour was not consistent).
Additionally, I also fixed that the Rotate event which is printed at the beginning, which does not exist physically in the binlog, is not printed anymore.
ChangeSet@1.1659.159.1, 2004-03-18 19:29:07+02:00, guilhem@mysql.com