Nathanael Nerode, on 2004-01-20, 12:12, you wrote: > Quite right; that's obviously the correct fix. > > Seems to me this is an important bug in fam, and I hope fam will be > fixed quickly. Would be, yes. But then we need to add a way to discover the socket's name to famd and libfam since this currently is only handled via RPC. Connecting to fam goes as follows: - ask portmap for program sgi_fam - connect to TCP port returned by portmap - ask for local connection on UNIX domain socket - connect to UNIX domain socket returned by the FAM As you can see, portmap plays an important role here. When I get around to successfully patching fam 2.7.0 to support dnotify I may try to patch it further, so it would provide a well known UNIX domain socket that could make portmap obsolete for local clients though this does not seem to be very easy. Regards, Joerg (fam maintainer) -- Joerg "joergland" Wendland GPG: 51CF8417 FP: 79C0 7671 AFC7 315E 657A F318 57A3 7FBD 51CF 8417
Attachment:
signature.asc
Description: Digital signature