Text 40671, 65 rader
Skriven 2006-10-04 10:13:37 av mark lewis (1:3634/12.0)
  Kommentar till text 40588 av Matt Bedynek (1:106/1)
Ärende: FNEWSN39
================
 ml> looks like i got two tics and only one snooze archive, the dudfile
 ml> one... it would appear that the processing on rossC's system overwrote
 ml> the original FNEWSN39.ZIP that was destined for my system...

 ml> that brings up another question that possibly no one can really
 ml> answer...

 ml>           what happens when a system has two files of the
 ml>           same name for a downlink?

 MB> binkd will rename the new file _if_ both files reside in the
 MB> inbound at the time of reception. 

yes... but i'm talking about after the tic processor has moved it into the
outbound directory for further transmission...

 MB> What I suspect really happened here is that ross recieved the 
 MB> first copy from bjorn and likely received the copy from janis 
 MB> before the original was sent to your system?  

yes... the question is how or why did the second copy overwrite the first
one... that would appear to be an error in the tic processing program or in a
script used to move the file to a filebox...

 MB> At least, I can see this happening since people usually store a 
 MB> file area in one place and their file tosser sends the file
 MB> directly from that directory.

i think i see what you are saying...

on my system, if i carry an area in my filebase, allfix puts the file into that
area unless it has another file of the same name and i've told it to not
overwrite or replace... that puts the file into my bbs' file areas...

now, if i also forward files in that area on to other systems, allfix creates
tic files which get placed into my TICOUT directory and the file is copied to
my TICHOLD area... it is right at this point that there could be a problem...
if there is already a file XYZ in TICHOLD, and another file of the same name is
processed for forwarding on, does the second XYZ file overwrite the first one
or what?

see, this is one of the problems that i know some mailer developers
contemplated quite deeply... they can have the mailer send the file XYZ to
another system with the name ABC... however, when it comes to tic files and
such, there's no provision that i can recall whereby a file is stored on a
system with one name and transmitted with another... FWIW: this same problem
also comes up with filenames that do not fit within the old DOS 8.3 naming
convention... it might be possible with certain outbound queues that certain
mailers support... i know that allfix works directly with frontdoor's STQ
(Static Transmission Queue) which does have the ability to store the local name
and the transmission name... however, none of this type of stuff works in a
binkley style setup...

[time passes]

owww, my aching head... i've just been wading thru the allfix docs and still
can't really tell if allfix will overwrite an outbound file with another one of
the same name :(  it appears that certain combination of options will help to
prevent this but not in all mailer type environments... BSO type mailers simply
loose out pretty much all around because they simply don't have the needed
abilities to handle intricacies such as this...

)\/(ark

 * Origin:  (1:3634/12)