Greetings.
Looks like my last comment to
http://groups.google.com/group/distcc-patches/browse_thread/thread/313c50b484639fc1
was silently dropped for some reason.
It would be nice if somebody could take a look at the updated patch
attached to
http://code.google.com/p/distcc/issues/detail?id=59#c8. I
fixed the coding mistakes pointed by Fergus and also implemented the
+zeroconf,cpp,lzo stuff in the hosts file. Right now I'm working on
the tests for the whole zeroconf bunch of features.
Before I change the manuals I'd like to know how to handle the "auth"
option I missed last time? I'd like option handling to be consistent
in the docs (well, and the code too, of course). Since I'm not
familiar with GSS-API the only place I could take as a guide was this
changeset:
http://code.google.com/p/distcc/source/detail?r=708 (btw,
will it be integrated upstream?). I guess I can handle "auth" option
just like cpp and lzo: whenever daemon is started with --auth it adds
the "auth" option to the options TXT field, and if client has
"+zeroconf,auth" in its hosts file as well such server will produce an
entry with the ",auth" option as well. Does this all make sense?
Regards, Ihor.