Path: utzoo!attcan!uunet!husc6!mailrus!purdue!decwrl!decvax!virgin!jbd From: jbd@virgin.UUCP (J. Bruce Dawson) Newsgroups: comp.mail.uucp Subject: Re: Rerouting considered GOOD Summary: Permitting and preserving site-local pathalias data Message-ID: <2241@virgin.UUCP> Date: 1 Oct 88 12:57:29 GMT References: <8809212215.AA21035@naggum.se> <2540@sultra.UUCP> <371@ditka.UUCP> <1988Sep27.105604.5152@ateng.ateng.com> <383@ditka.UUCP> Reply-To: jbd@virgin.UUCP (Bruce Dawson) Organization: Virgin Software, Ltd., Nashua, NH. Lines: 28 In article <383@ditka.UUCP> kls@ditka.UUCP (Karl Swartz) writes: >In article lear@NET.BIO.NET (Eliot Lear) writes: >>I say, ``Well I know there is bad data out there, and my solution will >>be to discover/research(/divine;-) better methods of update and >>propagation.'' > >And then you add that to your local pathalias input. > >Unless, of course, your methods identify *all* the rabid re-routers I frequently end up modifing the pathalias data manually to compensate for known bad links. However, this is a pain to do everytime I get a new pathalias database. What's wrong with a "pathalias search list"? This would work something like: 1) Look in local site's list of paths (say, /usr/lib/uucp/localpaths). If not found, then: 2) Look in network's list of paths (say, /usr/lib/uucp/paths). If not found, then issue a message. Comments? -- J. Bruce Dawson (603)880-1517 office (603)880-6629 home 33 Cortez Drive, Nashua, NH. 03062