Dallas Hinton wrote to All <=-
I'm looking for a way to control polling times on a node by node basis. I've some nodes that I poll on the 1/2 hour -- I've others I only want
to poll once or twice a day. Any idea how I can set this up? I'm
running Irex in Daemon mode, in windows.
Thanks!
I'm looking for a way to control polling times on a node by node basis. I've some nodes that I poll on the 1/2 hour -- I've others I only want to poll once or twice a day. Any idea how I can set this up? I'm running Irex in Daemon mode, in windows.
Thanks!
running Irex in Daemon mode, in windows.
Setup "events" in the Event Manager... using the -fs switches and
include the node address.
Dallas Hinton wrote to Bill McGarrity <=-
running Irex in Daemon mode, in windows.
Setup "events" in the Event Manager... using the -fs switches and
include the node address.
I guess I'm a bit dense -- -fs I don't think works for daemon mode? And
in that mode I don't see how to assign a particular event to a
particular node - it looks global! :-( What am I missing?
I also run in daemon as well. Open IRex config mgr.. scroll down to
Event Mgr... open it and hit "insert". A new box will appear. Give
it an event name and the days you want it to run and the times.
Then where it says Command line type: -fs <node address you want to
poll> without the <> Just make sure that node is in your node mgr
as well. That should do it. Make sure you also configure your
ROUTE.REX as well.
Dallas Hinton wrote to Bill McGarrity <=-
I also run in daemon as well. Open IRex config mgr.. scroll down to
Event Mgr... open it and hit "insert". A new box will appear. Give
it an event name and the days you want it to run and the times.
Then where it says Command line type: -fs <node address you want to
poll> without the <> Just make sure that node is in your node mgr
as well. That should do it. Make sure you also configure your
ROUTE.REX as well.
Thanks, Bill -- so what should the route.rex look like? I currently
have: =====================
route-to 1:138/0.0 1:138/*
route-to 1:342/0.0 1:342/*
route-to 1:343/3.0 1:343/*
Hold 1:153/7041
EVENT A
Unhold 1:153/7041
EVENT B
hold 1:153/7041
=============
And event manager for A says
all days, 00:00-24:00, run every 12:00 -fs 1:153/7041
Does that seem right? Thanks!
have: =====================
route-to 1:138/0.0 1:138/*
route-to 1:342/0.0 1:342/*
route-to 1:343/3.0 1:343/*
Hold 1:153/7041
I am assuming 1:138/0 is your hub? If so and you want to cover all
4 of Fido's zones for netmail, then try this:
route-to 1:138/0 1* 2* 3* 4*
except 1:342/*
route-to 1:342/0.0 1:342/*
except 1:343/*
route-to 1:343/3.0 1:343/*
HOLD 1:153/7041
EVENT A
Unhold 1:153/7041
You really don't need the above hold/unhold as it will stay in your outbound till the event A is run. The -fs stands for fetch and send.
IF that node were to connect to you, then it would go. If you don't
want the other node the ability to pick up mail then use the
hold/unhold option
EVENT B
hold 1:153/7041
Again, if you want to keep the node from retrieving their own mail
then leave this in. Just make sure event B runs right after A is
finished.
=============
And event manager for A says
all days, 00:00-24:00, run every 12:00 -fs 1:153/7041
So you're polling every 12 hours. rather a long stretch between mail
runs. :) But it looks good...
route-to 1:138/0.0 1:138/*
route-to 1:342/0.0 1:342/*
route-to 1:343/3.0 1:343/*
Hold 1:153/7041
EVENT A
Unhold 1:153/7041
EVENT B
hold 1:153/7041
=============
And event manager for A says
all days, 00:00-24:00, run every 12:00 -fs 1:153/7041
Dallas Hinton wrote to Bill McGarrity <=-
I am assuming 1:138/0 is your hub? If so and you want to cover all
4 of Fido's zones for netmail, then try this:
route-to 1:138/0 1* 2* 3* 4*
except 1:342/*
route-to 1:342/0.0 1:342/*
except 1:343/*
route-to 1:343/3.0 1:343/*
HOLD 1:153/7041
Ahh -- I'm beginning to see!!
EVENT A
Unhold 1:153/7041
You really don't need the above hold/unhold as it will stay in your outbound till the event A is run. The -fs stands for fetch and send.
IF that node were to connect to you, then it would go. If you don't
want the other node the ability to pick up mail then use the
hold/unhold option
EVENT B
hold 1:153/7041
Again, if you want to keep the node from retrieving their own mail
then leave this in. Just make sure event B runs right after A is
finished.
If I don't have the hold and unhold lines, then do I even need to
mention Event A and B in route.rex? There wouldn't be anything under
them!
=============
And event manager for A says
all days, 00:00-24:00, run every 12:00 -fs 1:153/7041
So you're polling every 12 hours. rather a long stretch between mail
runs. :) But it looks good...
Yes, that's the plan - I've one node who doesn't want me to hit him
very often, the others seem happy with the every 1/2 hour irex seems to
do by default!
Leave it in then... either way.. :)
That's strange... I can see if it was a POTS connection but binkd?
OK.. :)
I just so happened to read Joe's reply to you regarding transfer
protocol and he maybe onto something. IRex reports 1.1 but only
connects at 1.0. Check to see if your links are trying to connect
with 1.1 in your logs.
Dallas Hinton wrote to Bill McGarrity <=-
Leave it in then... either way.. :)
Oh.
That's strange... I can see if it was a POTS connection but binkd?
OK.. :)
That was my reaction! :-)
I just so happened to read Joe's reply to you regarding transfer
protocol and he maybe onto something. IRex reports 1.1 but only
connects at 1.0. Check to see if your links are trying to connect
with 1.1 in your logs.
No, every connect shows 1.1 - good idea though! :-)
So here's what the log shows -- I don't see the system "dialing" 7041
-- I must still have something wrong!
---------- Event A, Sat Apr 26 00:00:00 2014
+ 23:59:59 (996) Command line: -fs 1:153/7041
% 23:59:59 (996) Done.
% 23:59:59 (272) System: BETWEEN.BAT
% 00:00:06 (996) Starting event.
% 00:00:06 (996) Recalculating.
---------- Event B, Sat Apr 26 00:00:06 2014
+ 00:00:06 (996) Command line:
Is everything setup correctly in your node mgr for that node? Do a
ALT-F and type in the address and see if it connects that way. A
force may give more info.
Dallas Hinton wrote to Bill McGarrity <=-
Is everything setup correctly in your node mgr for that node? Do a
ALT-F and type in the address and see if it connects that way. A
force may give more info.
Oh yes, it connects just fine -- it's been working for a couple of
years, but the gentleman in question has decided he doesn't want to
talk to me that often. :-)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,042 |
Nodes: | 15 (0 / 15) |
Uptime: | 144:00:48 |
Calls: | 500,263 |
Calls today: | 1 |
Files: | 95,201 |
D/L today: |
104 files (65,589K bytes) |
Messages: | 464,618 |