cannot get idled to run

[Craig Constantine]

I'm running (compiled from source) Cyrus-imapd-2.1.13 on RedHat Linux 8.0 
[all patched up to date.]

With every incoming message I get the oft seen "error sending to idled" 
message in syslog facility local6. Cyrus is of course compiled to use 
idled.  :)

My cyrus.conf contains:
--------snip-----------
START {
  # do not delete this entry!
  recover       cmd="ctl_cyrusdb -r"

  # this is only necessary if using idled for IMAP IDLE
  idled         cmd="idled"
}
--------snip-----------

my /etc/imapd.conf contains:
--------snip-----------
idlesocket: /var/imap/socket/idle
--------snip-----------

/var/imap/socket/ looks like:
--------snip-----------
# ls -al /var/imap/socket/
total 8
drwxr-s---    2 smmsp    cyrus        4096 Nov 18 15:42 .
drwxrwsr-x   12 smmsp    cyrus        4096 Nov 18 15:50 ..
srwxrwxrwx    1 root     cyrus           0 Jun 17 22:24 idle
--------snip-----------

ps shows idled is in fact, not running. Sending the Cyrus master process a 
SIGHUP leaves this in my syslog -- no sign of idled 
starting/stopping/crashing:
--------snip-----------
Nov 18 16:07:42 portnoy master[7145]: got SIGHUP
Nov 18 16:07:42 portnoy tls_prune[7530]: tls_prune: purged 0 out of 0 
entries
Nov 18 16:07:42 portnoy ctl_cyrusdb[7532]: checkpointing cyrus databases
Nov 18 16:07:42 portnoy ctl_deliver[7531]: duplicate_prune: pruning back 3 
days
Nov 18 16:07:42 portnoy lmtpd[7419]: error sending to idled: 2
Nov 18 16:07:42 portnoy ctl_deliver[7531]: duplicate_prune: purged 28 out 
of 5854 entries
Nov 18 16:07:44 portnoy ctl_cyrusdb[7532]: done checkpointing cyrus 
databases
--------snip-----------

Thoughts? I even tried to start idled by hand:
--------snip-----------
# su - cyrus -c '/usr/cyrus/bin/idled -C /etc/imapd.conf'
bind: Address already in use
--------snip-----------

That explains why it doesn't start. But I don't understand why I'm getting 
a bind error on the unix socket... ?

The only thing (that I see) idled should be binding to is the unix socket 
named in imapd.conf via 'idlesocket'. But a netstat shows that the unix 
socket /var/imap/socket/idled is not in use, and invoking fuser on the 
sockets in /var/imap/socket confirms the idled socket is not inuse. (I 
fuser'd the lmtp socket to make sure fuser does what I think it does. -- 
7145 is the cyrus master at the moment. :)
--------snip-----------
# fuser lmtp
lmtp:                 7145  7584
# fuser idle
#
--------snip-----------

Anyone care to swing the clue bat at me?

-Craig