Subj : Re: skipping files (bug?) To : Oli From : Wilfred van Velzen Date : Sat Jan 02 2021 12:30 pm Hi Oli, On 2021-01-02 11:41:08, you wrote to All: Ol> How does file skipping work in Binkd? I'm on a bad/slow mobile Ol> connection Ol> at the moment and only want to receive mails, no nodelist updates. So I put Ol> skip all !0 DAILYUTF.* Ol> in binkd.cfg, but the file doesn't seem to get deleted on the other side: Ol> - 11:28 [1138] VER binkd/1.1a-111/Linux binkp/1.1 Ol> - 11:29 [1138] TRF 0 55671 Ol> + 11:29 [1138] Remote has 0b of mail and 55671b of files for us Ol> ? 11:29 [1138] skipping DAILYUTF.Z02 (destructive, 55671 byte(s), mask Ol> DAILYUTF.*) Ol> next poll it's still the same... Ol> - 11:31 [1146] VER binkd/1.1a-111/Linux binkp/1.1 Ol> - 11:31 [1146] TRF 0 55671 Ol> + 11:31 [1146] Remote has 0b of mail and 55671b of files for us Ol> ? 11:31 [1146] skipping DAILYUTF.Z02 (destructive, 55671 byte(s), mask Ol> DAILYUTF.*) Ol> until some mail is exchanged: Ol> - 11:37 [1159] TRF 0 55671 Ol> + 11:37 [1159] Remote has 0b of mail and 55671b of files for us Ol> + 11:37 [1159] sending /ftn/packets/f04ce901.pkt as f04ce901.pkt (1064) Ol> 11:37 [1159] bzip2 mode is on for f04ce901.pkt Ol> ? 11:37 [1159] skipping DAILYUTF.Z02 (destructive, 55671 byte(s), mask Ol> DAILYUTF.*) 11:37 [1159] Compressed 1064 bytes to 770 for f04ce901.pkt, Ol> ratio 72.4% Strange, on this end they look the same regarding the DAILYUTF file. This is what a grep on DAILYUTF.Z02 shows: + 02 Jan 08:50:06 [31959] sending /home/fido/fileareas/dailyutf/DAILYUTF.Z02 as DAILYUTF.Z02 (55671) 02 Jan 08:50:06 [31959] bzip2 mode is on for DAILYUTF.Z02 + 02 Jan 08:50:14 [31959] remote already has DAILYUTF.Z02 + 02 Jan 11:26:54 [6706] Status is 'DAILYUTF.Z02 55671 1609542303' + 02 Jan 11:26:54 [6706] sending DAILYUTF.Z02 as DAILYUTF.Z02 (55671) 02 Jan 11:26:54 [6706] bzip2 mode is on for DAILYUTF.Z02 + 02 Jan 11:27:01 [6706] remote already has DAILYUTF.Z02 + 02 Jan 11:28:29 [6721] Status is 'DAILYUTF.Z02 55671 1609542303' + 02 Jan 11:28:29 [6721] sending DAILYUTF.Z02 as DAILYUTF.Z02 (55671) 02 Jan 11:28:29 [6721] bzip2 mode is on for DAILYUTF.Z02 + 02 Jan 11:28:30 [6721] remote already has DAILYUTF.Z02 + 02 Jan 11:29:00 [6726] Status is 'DAILYUTF.Z02 55671 1609542303' + 02 Jan 11:29:00 [6726] sending DAILYUTF.Z02 as DAILYUTF.Z02 (55671) 02 Jan 11:29:00 [6726] bzip2 mode is on for DAILYUTF.Z02 + 02 Jan 11:29:01 [6726] remote already has DAILYUTF.Z02 + 02 Jan 11:31:01 [6776] Status is 'DAILYUTF.Z02 55671 1609542303' + 02 Jan 11:31:01 [6776] sending DAILYUTF.Z02 as DAILYUTF.Z02 (55671) 02 Jan 11:31:01 [6776] bzip2 mode is on for DAILYUTF.Z02 + 02 Jan 11:31:01 [6776] remote already has DAILYUTF.Z02 + 02 Jan 11:37:33 [7087] Status is 'DAILYUTF.Z02 55671 1609542303' + 02 Jan 11:37:33 [7087] sending DAILYUTF.Z02 as DAILYUTF.Z02 (55671) 02 Jan 11:37:33 [7087] bzip2 mode is on for DAILYUTF.Z02 + 02 Jan 11:37:34 [7087] remote already has DAILYUTF.Z02 Ol> next poll: Ol> - 11:37 [1172] TRF 0 0 Ol> + 11:37 [1172] Remote has 0b of mail and 0b of files for us Ol> Is this a bug? Maybe binkd gives up after a couple of retries? It seems to remember the transmit status of the file between sessions... Bye, Wilfred. --- FMail-lnx64 2.1.0.18-B20170815 * Origin: FMail development HQ (2:280/464) .