Xref: utzoo comp.mail.misc:3430 comp.mail.uucp:4316
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!samsung!rex!mb
From: mb@rex.cs.tulane.edu (Mark Benard)
Newsgroups: comp.mail.misc,comp.mail.uucp
Subject: Re: pathalias breaks on latest map distribution - HELP!
Message-ID: <3438@rex.cs.tulane.edu>
Date: 29 May 90 21:36:12 GMT
References: <1990May29.182555.27806@pmsmam.uucp>
Organization: Computer Science Dept., Tulane Univ., New Orleans, LA
Lines: 24

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 had the same problem and tracked it down to an infinite loop involving
bcsinc (in u.usa.ca.1) and rt1 (in u.usa.nm.1).  Since the NM map was not
changed recently and that CA map arrived last night, I concluded that it was
a problem with bcsinc.  Sure enough, commenting the bcsinc entry out of the
CA map solved the problem.

However, I do not know exactly why the loop occurred.  Can anyone explain?

Mark
-- 
Mark Benard
Department of Computer Science     INTERNET & BITNET: mb@cs.tulane.edu
Tulane University                  USENET:   rex!mb
New Orleans, LA 70118