From: mark@infocomm.com
Newsgroups: vmsnet.uucp
Subject: Re: HELP!!! Multiple versions in uucp_spool:d.*
Date: 6 Nov 92 16:21:36 GMT
Organization: INFO COMM - Computer Consulting, Redwood City, Ca

In article <1992Nov5.222054.4328@spcvxb.spc.edu>, terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.) writes:
> In article <1992Oct28.091547.17761@infocomm.com>, mark@infocomm.com writes:
>> Your Immediate work around:
>>
>> 	$ DELETE UUCP_DATA:SEQUENCE.NUMBER;1
>>
>> Do this once every few weeks to avoid the problem.  The next release will fix
>> this.
>
>   I got bit by this problem yesterday. I deleted the SEQUENCE.NUMBER;1 file
> and things looked good for a few hours (sequences went down to things like
> 00C), but the problem seems to be back. My sequence numbers jumped back up
> to things like 6CQ and I'me getting duplicate versions.

You certainly DON'T want to do the "$ DELETE UUCP_DATA:SEQUENCE.NUMBER;1"
too often or you can get duplicate versions of you still have UUCP traffic
queued based on the "last time" you reset the sequence number.

If you indeed have "new" jobs with sequence numbers of "6CQ" already, then
something else strange is going on.  "6CQ" represents approximately
6*36*36+13*36+17 or 8261 which, although high, should not be close to "O07"
(32767) which is the largest value that would not cause a problem.

>   Is there anything else that could be happening?

It seems so, but I'm not yet sure what it is.  Exactly what do you mean by
"getting duplicate versions".  What are some examples of the files in question?
what is the current contents of UUCP_DATA:SEQUENCE.NUMBER as shown with the VMS
DUMP command?

>   Also, I'd like to make two suggestions:
>
>   1) I think that in V1.x the files all had the destination system's name,
>      while in V2.0 the C file has the destination's name, but the B and D
>      files have the local hosts's name. The old way made it easier to see
>      at a glance what was going where, and by doing a DIR UUCP_SPOOL:D.host-
>      name*/size I could see how much was queued for a particular site.

Since we originally released UUCP, the only way the file naming scheme has
changed along these lines (i.e. which hostname is used), was very early on with
UUX_RNEWS.  I think this was in 1.1 and "fixed" in 1.2.  There is good reason
for which name is being used for the files that get stored on the remote
computer.  The sending computer is not sure what "spool directory" management
scheme is being used on the remote system and how many remote systems the
remote site is using.  If all sites sending traffic to a particular remote
system end up dumping their traffic into the same directory AND the file names
being used are derived from the names of the destination system instead of the
originating system, there exist much greater likelyhood of file naming
collisions and what follows then is chaos.  :-)

If you are interested in knowing how much traffic is queued for all of your
neighbor systems (or a particular one), the following command is useful:

	$ uustat -q [-s sitename]

>   2) Can the SEQUENCE.NUMBER patch, the $GETDVI/LAT hangup patch, and any of
>      the other high-priority patches be compiled and the changed executables
>      placed in a UU20FIXES.BKP saveset? Then the FTP sites (mine included)
>      and Hunter's MAILSERV could make it available for those without the needed
>      compilers/time?

Sounds like a good idea, we'll look into it.

--
Mark Pizzolato - INFO COMM Computer Consulting, Redwood City, Ca
PHONE:	(415)369-9366	UUCP:  decwrl!infopiz!mark or uunet!lupine!infopiz!mark
DOMAIN:	mark@infocomm.com