diff options
| author | Edward Betts <edward@4angle.com> | 2018-09-25 17:46:28 +0100 |
|---|---|---|
| committer | Omer Katz <omer.drow@gmail.com> | 2018-09-25 19:46:28 +0300 |
| commit | c77c62651b8974b8d3c738467138250078c112fe (patch) | |
| tree | 04df2ff2395275e27293af5fca38df182b876e44 /TODO | |
| parent | 24f73c5cd8f839bd520eb52e91d0d26e07689373 (diff) | |
| download | distcc-git-c77c62651b8974b8d3c738467138250078c112fe.tar.gz | |
Correct spelling mistakes. (#286)
I'm going to merge this. It seems correct.
Thanks for the contribution.
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -19,7 +19,7 @@ failing to resolve a host should be a soft failure State files depend on host byte order and break when DISTCC_DIR is -shared between heterogenous machines. Of course sharing this +shared between heterogeneous machines. Of course sharing this directory is probably a bad idea anyhow. @@ -1049,7 +1049,7 @@ central configuration would be good, and probably quite practical. Setting up a list of machines centrally rather than configuring each one sounds more friendly. The most likely design is to use DNS SRV records (RFC2052), or perhaps - multi-RR A records. For exmaple, compile.ozlabs.foo.com would resolve to + multi-RR A records. For example, compile.ozlabs.foo.com would resolve to all relevant machines. Another possibility would be to use SLP, the Service Location Protocol, but that adds a larger dependency and it seems not to be widely deployed. |