Subj : Re: mis not running on schedule
To   : ogg
From : Avon
Date : Fri Mar 01 2024 06:00 pm

On 26 Feb 2024 at 11:17p, ogg pondered and said...
 
 og> 2) If you've got your node set up in the "Echomail Nodes" (under
 og> Networking) option, then you should be able to just enter an hourly
 og> event.  Under "Shell", I use "mis poll forced" and that polls all of my
 og> nodes.

This forces a poll to all active echonodes each time even if no traffic is waiting to be sent to them. To be honest it's not a method I use.

I've got my events setup to poll echomail node hubs specifically (which is just a choice thing) e.g. mis poll 21:1/100 | mis poll 3:770/1  

Another option is to define certain key echomail nodes (the HUBs you want to poll each time to check for packets etc.) as 'uplinks' in their individual echomail node setup... then in the events system run a sell line such as 'mis poll uplink binkp' for example and all of those systems are polled in one each move.

:)

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going'
avon[at]bbs.nz | bbs.nz | fsxnet.nz 

--- Mystic BBS v1.12 A48 (Linux/64)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.