Subj : File, file; who's got the To : David Calafrancesco From : Ross Cassell Date : Fri Aug 31 2001 02:10 am Hello David! 31 Aug 01 01:10, you wrote to me: RC>> Nothing of yours is being modified, ALLFIX here doesnt even do RC>> virus scan or care for ZIP file comments, everything is passed on RC>> as it is received. DC> Then why is it not propogating the way it was expected when it was DC> hatched? By analogy, we could edit any in-transit TIC file and DC> redirect it to what we felt were more appropriate fileareas, DC> regardless of what the hatcher desired when hatching the file. Why dont you investigate the magicfilename function of Allfix, I believe you use it, its got lots of uses, for instance one facet of it I use is pertinent to the weekly nodediff, when nodediff.a?? comes in the nodediff FDN, I have this magicfilename call the unarchiver which deposits the raw diff into my nodelist directory, then fastlist does the rest. RC>> What really is flabergasting you is that my downlinks are not RC>> subservient to the votes of the Z1B. DC> No, what is flabergasting me is that a HUB like yourself and Jack DC> would edit in-transit traffic to alter it's distribution from what was DC> intended by the hatcher. What your hatcher intends and what you all voted on is the issue here. RC>> I do not recall anyone condoning that action. Prove it! DC> Really? What do you call it when an appointed officer of the zone is DC> caught red handed doing something so verbotin (we have specific DC> mention of similar examples in our policy document resulting in DC> excommunication) yet months later is still in that same office and DC> still controlling the 'official' routelist. Bullshit, you all wanted her out of office because of the + signs long before that. DC> had our head on a platter so fast. Hell, she is ready to lynch Todd DC> just because he was frustrated and blowing off steam in what he DC> thought was a private echo. DC> Too bad too, because what he was talking about doing was adding new DC> quality content to the file system, but now there is no way in hell he DC> will ask for the FDN he was considering creating. If he does offer the DC> content to the zone, it probably won't be through the filegate system, DC> by his own choice. Todd made similiar comments in netmail to me.. They werent worded as steam blowing off either.. RC>> Perhaps you are unaware that the person who hatched the latest RC>> file IRNROUTE.238, screwed it up so badly that it didnt propogate RC>> properly? DC> Yup... I wasn't aware... I suppose shit happens... Indeed it does, when it happens to you all, its ok, if it happens to others, kill, kill, kill! DC> Sounds like someone's system wasn't disengaging cleanly and caused DC> multiple re-sends creating multiple copies. I have seen the same thing DC> happen here on occasion. Certain internet problems can cause file DC> transfers to not end cleanly (the final ACK is lost) triggering a DC> whole new XMIT, which depending on the receivers config either DC> overwrites, or increments the file. Sounds like in the effort of DC> dealing with backlogged dupes, the receiver chose to increment (I do DC> that too). I checked further, you will forgive me if the first thought that crossed my mind was a seenby issue or that perhaps that Dales file link might have disengaged the backbone FDN from Janis.. I learned that the chart was hatched by reading the file announcement of one of Dales direct downlinks in a regional echo... I checked my system thoroughly, nothing trapped in the inbound or badtic (in case it was a crc anomaly). I back tracked to Janis, she performed the same checks, she didnt have it either. I logged onto the ftp server of Dales file uplink and found the file, he apparently didnt know what to do, so he put it up for download. Janis finished the investigation, the rest you know. == Ross http://www.the-estar.com:8080 ross@the-estar.com or rcassell@home.com ICQ = 5305939 --- GoldED/W32 3.0.1 * Origin: The Eastern Star [Mail Hub] - 864.573.7069 (1:18/500) .