MySQL Replication Master Not Logging Changes In Binlog?

The following setup is on MySQL 4.0.16 on Debian LINUX.

It appears as if my replication master is not logging changes to any databases. My my.cnf is as follows:

Code:
server-id               = 154
log-bin                 = /var/log/mysql/mysql-bin.log
binlog-do-db            = dollars
The server status is great.

Code:
File            Position   Binlog_do_db    Binlog_ignore_db
mysql-bin.005   4          dollars,epoch
The slave connects correctly, and waits patiently for updates. The master logs the slave connecting, but gives it nothing.

I'm certainly using the correct database, and my transactions are being commited. I've tried MyISAM and InnoDB tables, and neither are shown.

Here is a sample query:

Code:
use dollars ;
create table Bobby
  (
  id int unsigned primary key auto_increment,
  ssn int
  ) type=InnoDB ;
insert into Bobby (ssn) values (12312),(12312544),(1231231);
commit ;
Now, the binlogs before the query are as follows:

Code:
lukas@localhost:/var/log/mysql$ dir
total 28
drwxrwxrwx    2 dollars  mysql        4096 Dec  1 21:53 ./
drwxr-xr-x    9 root     root         4096 Dec  1 06:52 ../
-rw-rw----    1 dollars  users        1271 Dec  1 21:36 mysql-bin.001
-rw-rw----    1 dollars  users         655 Dec  1 21:59 mysql-bin.002
-rw-rw----    1 dollars  users          58 Dec  1 21:49 mysql-bin.index
-rw-rw----    1 dollars  users         348 Dec  1 21:49 mysql-slow.log
After the preceding code block, the binlogs have increased.

Code:
lukas@localhost:/var/log/mysql$ dir
total 24
drwxrwxrwx    2 dollars  mysql        4096 Dec  1 21:59 ./
drwxr-xr-x    9 root     root         4096 Dec  1 06:52 ../
-rw-rw----    1 dollars  users        1271 Dec  1 21:36 mysql-bin.001
-rw-rw----    1 dollars  users         904 Dec  1 22:02 mysql-bin.002
-rw-rw----    1 dollars  users          58 Dec  1 21:49 mysql-bin.index
-rw-rw----    1 dollars  users         348 Dec  1 21:49 mysql-slow.log
As you can see, the bin.002 log increased from 655 bytes to 904 bytes. However, running mysqlbinlog on the 002 file STILL produces nothing:

Code:
lukas@localhost:/var/log/mysql$ mysqlbinlog mysql-bin.002
# at 4
#031201 21:49:39 server id  154         Start: binlog v 4, server v  created 691231 19:00:00
There are two things I notice about this output. First, the last part "created 691231 19:00:00" is 7pm on New Years Eve 1969. Is this coincidentally near the epoch, or was this a missed compiled time? I don't think this should be the time of the binlog creation....

The second thing I notice..... well.... the second thing I notice is the damn thing isn't working. So someone help me.... please?

Lukas