Hello Sean!

22 Apr 06 18:34, Sean Dennis wrote to All:


 SD> maxp max -s%1 -b%2 -p%3 -n1 -t60 -e1 -lnode1.log

 SD> The -t is for the time length for each call (forced).  What I'd like
 SD> to do is to write a REXX script that would determine if it's between 6
 SD> AM and 10 PM, to allow 60 minutes only and if it's between 10 PM and 6
 SD> AM, to allow them the full use of their access level's time limit.

The idea behind "-t" is for the mailer to communicate to the BBS
the time remaining to the next forced event in the mailer's schedule.  The
BBS then compares how much time there is until the mailer is supposed to do
something significant and how much time the caller is allowed by his user
profile and allows him to be on for the lesser of the two.  If you have a
5PM event, and the caller calls at 4:50, he should get 10 minutes...not an
hour (or two), or the 5PM event may not happen.  That's why it is normally
passed as a parameter (-t%4) rather than a hard-coded value.  -t can only
shorten a call, so if your users' profiles are currently set to 1hr and
Bink says 2 is OK...they still only get 1.

I would suggest using the BBS setup to limit the caller time, rather than
messing with the mailer.  You could use a commandline search-n-replace to
change the cumalative time allowed for whatever your default priv level is
(probably "Disgrace") within MAX.CTL, or have two alternate CTLs
and XCOPY the appropriate one over the "live" one.  It's a
one-liner in batch either way and then a re-SILT step to activate the
change.  Then you can create Bink events that attach those couple of lines
to errorlevel exit routines at 6AM and 10PM and solve your "I need to
know what time it is" problem without REXX routines.

Of course, you'll want to use that -t%4 in SPAWNBBS to make sure that those
events actually happen at the time you want them to. ;)

.\\ike

--- GoldED 2.50+