How does file skipping work in Binkd? I'm on a bad/slow mobile
connection
at the moment and only want to receive mails, no nodelist updates. So I put
skip all !0 DAILYUTF.*
in binkd.cfg, but the file doesn't seem to get deleted on the other side:
- 11:28 [1138] VER binkd/1.1a-111/Linux binkp/1.1
- 11:29 [1138] TRF 0 55671
+ 11:29 [1138] Remote has 0b of mail and 55671b of files for us
? 11:29 [1138] skipping DAILYUTF.Z02 (destructive, 55671 byte(s), mask DAILYUTF.*)
next poll it's still the same...
- 11:31 [1146] VER binkd/1.1a-111/Linux binkp/1.1
- 11:31 [1146] TRF 0 55671
+ 11:31 [1146] Remote has 0b of mail and 55671b of files for us
? 11:31 [1146] skipping DAILYUTF.Z02 (destructive, 55671 byte(s), mask DAILYUTF.*)
until some mail is exchanged:
- 11:37 [1159] TRF 0 55671
+ 11:37 [1159] Remote has 0b of mail and 55671b of files for us
+ 11:37 [1159] sending /ftn/packets/f04ce901.pkt as f04ce901.pkt (1064)
11:37 [1159] bzip2 mode is on for f04ce901.pkt
? 11:37 [1159] skipping DAILYUTF.Z02 (destructive, 55671 byte(s), mask DAILYUTF.*) 11:37 [1159] Compressed 1064 bytes to 770 for f04ce901.pkt, ratio 72.4%
next poll:
- 11:37 [1172] TRF 0 0
+ 11:37 [1172] Remote has 0b of mail and 0b of files for us
Is this a bug?
Strange, on this end they look the same regarding the DAILYUTF file. This is what a grep on DAILYUTF.Z02 shows:[...]
+ 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
next poll:
- 11:37 [1172] TRF 0 0
+ 11:37 [1172] Remote has 0b of mail and 0b of files for us
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...
Wilfred wrote (2021-01-02):
Strange, on this end they look the same regarding the DAILYUTF file. This
is what a grep on DAILYUTF.Z02 shows:
[...]
+ 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
next poll:
- 11:37 [1172] TRF 0 0
+ 11:37 [1172] Remote has 0b of mail and 0b of files for us
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...
That's weird/interesting. I removed the skip line in binkd.cfg and none of the skipped files is offered
anymore (at least it doesn't show up in my log). Are there still in your outbound for my system? I
thought destructive would mean that they are deleted from the remote outbound.
Strange, on this end they look the same regarding the DAILYUTF file.[...]
This is what a grep on DAILYUTF.Z02 shows:
+ 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
next poll:
- 11:37 [1172] TRF 0 0
+ 11:37 [1172] Remote has 0b of mail and 0b of files for us
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...
That's weird/interesting. I removed the skip line in binkd.cfg and none of the skipped files is offered anymore (at least it doesn't show up in my log). Are there still in your outbound for my system? I thought destructive
would mean that they are deleted from the remote outbound.
Maybe binkd gives up after a couple of retries? It seems to
remember the transmit status of the file between sessions...
That's weird/interesting. I removed the skip line in binkd.cfg and
none of the skipped files is offered anymore (at least it doesn't show
up in my log). Are there still in your outbound for my system? I
thought destructive would mean that they are deleted from the remote
outbound.
How does this "hold-skipped" work? Does it hold skipped files no matter what?
=== Cut ===
#
# hold-skipped <S>
# Binkd will hold for S seconds all mail skipped by a node. (Def. -- 1h)
#
#hold-skipped 1h
=== Cut ===
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,050 |
| Nodes: | 15 (0 / 15) |
| Uptime: | 57:05:24 |
| Calls: | 236,050 |
| Calls today: | 9 |
| Files: | 60,363 |
| D/L today: |
13,649 files (2,452M bytes) |
| Messages: | 289,520 |
| Posted today: | 6 |