Tru64 sockets bug?

[Jonathan Burelbach]

We are using rsync to maintain a warm mirror of our boot disks.  I just
updated to rsync 2.6.0 and noticed that the rsync runs are now getting
errors when copying sockets.  The system is running Tru64 5.1A pk 4 on 
an AlphaServer 4100.  Is this a bug?  Is there some way to not copy 
sockets or should I find all of them and add them to the exclude file?
rsync was built using a straight ./configure with no options and passed
all the tests once built.

TIA,
  Jon


>>> rsync --version
rsync  version 2.6.0  protocol version 27
Copyright (C) 1996-2004 by Andrew Tridgell and others
<http://rsync.samba.org/>
Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, 
              no IPv6, 32-bit system inums, 64-bit internal inums

rsync comes with ABSOLUTELY NO WARRANTY.  This is free software, and you
are welcome to redistribute it under certain conditions.  See the GNU
General Public Licence for details.


>>> ls -l /usr/var/cluster/members/member0/agentx/master 
srwxr-xr-x   1 root     system         0 Feb  4 13:10 /usr/var/cluster/members/member0/agentx/master=


rsync output:

building file list ... done
adm/rsync.system.log
adm/sialog
mknod "/bkvar/cluster/members/member0/agentx/master" failed: Invalid argument
cluster/members/member0/evm/evmlog/evmlog.20040213
mknod "/bkvar/cluster/members/member0/evm/sockets/evmd" failed: Invalid argument
cluster/members/member0/run/sudo/jburelba/10

wrote 27550211 bytes  read 420 bytes  1281424.70 bytes/sec
total size is 555819562  speedup is 20.17
rsync error: some files could not be transferred (code 23) at main.c(632)
var rsync completed 02/13/04 13:21:46




-- 
=========+=========+=========+=========+=========+=========+=========+
Jonathan Burelbach                               jburelba at mail.nih.gov
Unix Systems Administrator                  jburelba at topaz.cit.nih.gov
NIH/CIT/DCSS/SOSB;12 South Dr.;Bldg 12B/2N207;Bethesda  (301) 496-7372