🚀 go-pugleaf

In article <dave.08d6@ccom.co.nz> dave@ccom.co.nz (David Eaves) writes:
> I have had a news batch arrive which uuqxt/rnews failed to process.  The
> problem is that uuxqt spawns rnews with an incorrect filename so that
> rnews is unable to find the file to process.	I am running AmigaUUCP
> 1.17 beta 4.

Hmmm.

> The X. file from my provider is as follows:
>
>   U root southern
>   F D.southerd01bt
>   I D.southerd01bt
>   C rnews
>
> However the file in my spool dir is actually D.southerd01btt (note the
> extra 't' at the end).
>
> Where could the problem lie here?  Could it have anything to do with
> AmigaUUCP's case munging, or is the providers software at fault here
> (they are running on a Sun using Taylor UUCP I think)?

I don't _think_ it's with the case munging. The code in uuxqt tries to
lock the un-munged filename first:

	/*
	**  If unable to find file it could be munge-cased
	*/
	if (lock = Lock (dfile, SHARED_LOCK))
		UnLock (lock);
	else
		mungecase_filename (dfile, dfile);

been this way for quite a while.
--
  //   Michael B. Smith
\X/    mbs@adastra.cvl.va.us