🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: vmsnet.mail.mx
Article #268

Re: Problems with UUCP and MX

#268
From: jeh
Date: Fri, 16 Oct 1992 09:27
49 lines
3103 bytes
In article <1992Oct14.084936.309@cutler>, john@cutler.com (John E. Babbitt Jr.) writes:
> In article <1bdjbmINNq28@golem.wcc.govt.nz>, brockie@golem.wcc.govt.nz (Roger Brockie) writes:
>> 
>> The following is an extract from the uucp_log:uuxqt.log file.
>> Has anyone seen this problem before ?
>> [...]
>> $	    RMAIL DUA12:[UUCP.SPOOL.TOSH]D.TOSH19576; "brockie@med.wcc.govt.nz"
>> %RMS-F-FLK, file currently locked by another user
>> %TRACE-F-TRACEBACK, symbolic stack dump follows
>> module name     routine name                     line       rel PC    abs PC
>> MX_RMAIL        MX_RMAIL                          127      00000033  00001C47
>> $ FAILED_RMAIL:
>> Attempt to send mail to <brockie@med.wcc.govt.nz> failed with status %X1001828C
>> %RENAME-I-RENAMED, DUA12:[UUCP.SPOOL.TOSH]X.TOSH19576;1 renamed to DUA12:[UUCP.SPOOL.TOSH]REMAIL_X.TOSH19576;1
> 
> If only I could've seen the first few lines of the uucp log just prior to
> the above, I may have had an answer for you.
> 
> I've seen where some uucp software attempts to send the X file first, then
> the D file after.  Of course, the X get processed immediately (or it used
> to in pre-2.0) and one of the two things happen: 1) doesn't find the D.*
> file; 2) Finds the D. file as it's being renamed from a temporary name
> (and it's still locked by the renaming process).  The odds of 2) happening
> is very small, I must admit.
> 
> The uucp software that sends the X first then D is called "Coherent". 

I've never seen this nor heard a report on it before. Mr. Babbitt's conjecture
sounds like the right one.  

if the remote system sends the files in the correct order (D-file first) 
there is no way this can happen.  uucico does not send back the "file received
ok, what now?" message (CY message; see the protocol document) until after the
rename is DONE.  Until the remote sees this message it won't start to send
the next file.  So it looks very much as though the X-file arrived first.

There is no change in 2.0 re. X-file processing -- once the X-file arrives,
it gets processed.  

However, note what happened to the X-file -- it got renamed to
REMAIL_X.whatever.  It will be picked up again within an hour or so by the mail
delivery retry mechanism (part of uuclean.com).  By that time (!) the D file
should be present.  

	--- Jamie Hanrahan, Kernel Mode Consulting, San Diego CA
uucp 'g' protocol guru and release coordinator, VMSnet (DECUS uucp) W.G., and 
Chair, VMS Programming and Internals Working Group, U.S. DECUS VAX Systems SIG 
Internet:  jeh@cmkrnl.com, hanrahan@eisner.decus.org, or jeh@crash.cts.com
Uucp:  ...{crash,eisner,uunet}!cmkrnl!jeh
Technical Details
Message-ID: <1992Oct16.022724.759@cmkrnl.com>
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ucselx!crash!cmkrnl!jeh
References: <1bdjbmINNq28@golem.wcc.govt.nz> <1992Oct14.084936.309@cutler>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ucselx!crash!cmkrnl!jeh
From: jeh@cmkrnl.com
Newsgroups: vmsnet.mail.mx,vmsnet.uucp
Subject: Re: Problems with UUCP and MX
Message-ID: <1992Oct16.022724.759@cmkrnl.com>
Date: 16 Oct 92 02:27:24 PDT
References: <1bdjbmINNq28@golem.wcc.govt.nz> <1992Oct14.084936.309@cutler>
Organization: Kernel Mode Consulting, San Diego, CA
Lines: 49