On 16 Sep 2021 at 12:25p, g00r00 pondered and said...

A: Uplink flag that you can set Yes/No" and then a "poll uplink" option

I'd go with this option. Good to still have an option for force poll
everything

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 16 Sep 2021 at 01:28p, Jay Harris pondered and said...

I would vote for A and/or be able to specify more than address on the command line with ./mis poll, e.g:

./mis poll (address 1) (address 2) (address 3) etc

Perhaps a way forward if g00r00 opts to look at this would be to be able to create a special ini or txt file that contains the list of nodes and or syntax in it that is read by mis poll and then executed as a poll?

Ideally it could use some wildcard notation or certain keywords (like FastEcho does in it's routing file) to simplify which systems are polled when the txt file is read my mis poll.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

I know ifcico (as an example) offers "Hold" (really hold) and "NoHold" (send held packets if we initiated the session). Not sure how binkd handles things like this.

Yeah it am thinking it may just be that Mystic should not be polling any node marked as "Export type: Hold" even when forced is used, unless the address itself is supplied on the command line "mis poll 1:1/1"

I did like someone's suggestion about being able to supply multiple addresses on the poll command like "mis poll 1:1/1 10:1/1" etc so I might look into doing that as well.

It seems the few responses have suggested either option A or this command line change. Maybe both would be good!? I'll have to look at the code when I can get some time and see how easy it'd be to do this.

... Error, no Keyboard - Press F1 to Continue.

--- Mystic BBS v1.12 A47 2021/08/29 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)