🚀 go-pugleaf

In article <1990May29.182555.27806@pmsmam.uucp> wwm@pmsmam.uucp (Bill Meahan) writes:

> Since the latest distribution I've received from comp.mail.maps, my attempts
> to build a new pathalias database result in pathalias hanging forever while
> taking up about 4.5 MEGS of core.
> 
> After spending far too much time chasing the problem, I've found that
> keeping u.usa.nm.1 out of the input stream solves(?) the problem.  Apparently
> something in the lastest bunch of maps (which do NOT include nm.1 so far)
> is inconsistent with the Apr 25 version of u.usa.nm.1.

I ran into exactly the same problem.  The version of pathalias I've been
using (pathalias9) runs into a loop... it cycles repeatedly between
nodes "rt1", "rt1.lanl.gov", and "bcsinc".  rt1 and rt1.lanl.gov are one
and the same, and there's a bi-directional private dead link between rt1
and bcsinc.

I have no idea why this particular combination causes pathalias to
loop... it seems that it should work properly.

I was able to resolve (work around) the problem by downloading the
latest version of pathalias from uunet (~/mail/pathalias.Z).  This is a
more recent version than the one I had been using... it supports the
"adjust" clause, rather than the "-a" command-line option.  It seems to
"eat" the current maps distribution without any distress.

Ghu alone knows why it fixes things, though.

-- 
Dave Platt                                             VOICE: (415) 493-8805
  UUCP: ...!{ames,apple,uunet}!coherent!dplatt   DOMAIN: dplatt@coherent.com
  INTERNET:       coherent!dplatt@ames.arpa,  ...@uunet.uu.net 
  USNAIL: Coherent Thought Inc.  3350 West Bayshore #205  Palo Alto CA 94303