super slow client startup [partial solution]

I've been using the cvs version of sfs (0.8pre) with a decent amount
of success for a month or two now, but had seriously problems with the
amount of time it would take for the client to start. The time would
range from 20-50 minutes before the client initialized.

I finally got a little time to take a look at it using strace and
found that it was repeatedly pausing on a select statement for a
_very_ long time. After examining some of the file descriptors, I
found that one of them was a socket opened to 127.0.0.1. On a hunch I
started an NFS server on my local machine and ran the client. It
started instantly.

From my understanding of the way sfs works and certainly from the
documentation (http://www.fs.net/sfswww/sfs.html#Quick%20client%20setup),
this should not be necessary. While the improved startup time means I
can start using sfs for more things, the security-minded part of me is
a little concerned at having to run an NFS server on every client
machine.

Is this the way it is supposed to work, or is this just a consequence
of using the current development tree?

Matt