why is the remote backup still writing it's indexes locally?

Mr. Gieben, 
   First of all, this program rocks - thanks for
writing it. It's really ideal for my needs - not too
complex, and still flexible. I was starting to read
about Amanda and it was overkill for what I needed.
    
   I'm wondering about one thing, though. I'm doing
remote backups from a couple of servers to a central
one with cron jobs  - "monthly @[email protected]", etc.. 
   I noticed, though, that the file indexes
(inclist.monthly), etc., are being written locally to
the machine though, and not to to the remote host
along with the data.  To get around that, I made a
little script to scp them over after the backup with
the "postrun" directive.  Is there something I'm doing
wrong here?
 

Here's a copy of my hdup.conf. The indexes are being
written to /vol/backups on the local machine.


Thanks very much!
Tom Klopf


----------------------------------
[global]
archive dir = /vol/backups
date spec = iso
tar = /bin/tar
compression = bzip
compression level = 9
exclude = lost+found, /proc, /dev, /sys, /mnt,
/backups, /var/lib/mysql, /var/log, /backups_outgoing,
/iso
always backup = on
skip = on
force = no
overwrite = on

# my own host, backup this all important directory
[ns1]
# dont bother with mysql - its backed up seperately
with hotcopy
exclude = lost+found, /proc, /dev, /sys, /mnt,
/backups, /var/lib/mysql, /var/log, /backups_outgoing,
/iso
dir = /
chunk size = 650m
allow remote = yes
proto = /usr/bin/ssh
remote hdup = /usr/local/sbin/hdup
remote hdup option = -c /etc/hdup/hdup.conf
postrun = /root/bin/posthdup.sh
----------------------------------




__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html