🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: vmsnet.mail.mx
Article #266

Re: Problems with UUCP and MX

#266
From: John E. Babbitt Jr.
Date: Wed, 14 Oct 1992 15:49
43 lines
2692 bytes
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 ?
> 
> ...
> p:uxqt =< h:-       [10/13-14:54:05-2020411e]   Processing     (DUA12:[UUCP.SPOOL.TOSH]X.TOSH19576;1) u:-       
> p:uxqt << h:tosh    [10/13-14:54:06-2020411e]   Executing      (rmail brockie@med.wcc.govt.nz < UUCP_DISK:[UUCP.SPOOL.tosh]D.TOSH19576 > NL:) u:-       
>   Begin X file DUA12:[UUCP.SPOOL.TOSH]X.TOSH19576;1 at 13-OCT-1992 14:54:06.46
> $	    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
> ...
> 
> Roger
> -- 
> brockie@golem.wcc.govt.nz

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". 
Perhaps they've fixed it by now, but it was a problem for Coherent user a
year ago.  Suffice to say this user no longer runs that software.

Regards,

John E. Babbitt, Jr.        {UUCP: ...hplabs!hp-pcd!orstcs!cutler!john}
Senior Programmer/Analyst   {Internet: john@cutler.com}
Cutler & Company, Inc.      {Phone: 503/770-9000 (voice) 503/770-9014 (tt)}
Medford, Oregon  97504      {Disclaimer: What I say is my personal opinion}
Technical Details
Message-ID: <1992Oct14.084936.309@cutler>
Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!agate!usenet.ins.cwru.edu!gatech!swrinde!sdd.hp.com!ux1.cso.uiuc.edu!umn.edu!news.orst.edu!orstcs!cutler!john
References: <1bdjbmINNq28@golem.wcc.govt.nz>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!agate!usenet.ins.cwru.edu!gatech!swrinde!sdd.hp.com!ux1.cso.uiuc.edu!umn.edu!news.orst.edu!orstcs!cutler!john
From: john@cutler.com (John E. Babbitt Jr.)
Newsgroups: vmsnet.mail.mx,vmsnet.uucp
Subject: Re: Problems with UUCP and MX
Message-ID: <1992Oct14.084936.309@cutler>
Date: 14 Oct 92 08:49:36 PDT
References: <1bdjbmINNq28@golem.wcc.govt.nz>
Organization: Cutler & Company, Inc., Medford OR (503) 770-9000
Lines: 43