Hello, All.

I'm having problems with a single nightly event running at the wrong (very wrong!) time. I have but a single EVENTS00.BBS file for the entire system which is one dialup node and three telnet. The line in question:

Event All 0200 exit=105

For some reason, this event is running at varied times between 0800-0900. Do I
have something wrong in the events file?

Later,
Sean

... Any simple idea will be worded in the most complicated way.
--- GoldED/2 3.0.1
* Origin: Paragon BBS - 423.926.7999 - paragon.darktech.org (1:18/200)

Sean,

Event All 0200 exit=105

For some reason, this event is running at varied times between 0800-0900. Do I have something wrong in the events file?

Could it be that your system has a problem with GMT-settings which indeed provide for a 6hr or so separation?

\%/@rd

--- D'Bridge 3.59
* Origin: Many Glacier / WikiLeaks http://213.251.145.96 / (2:292/854)

Hi Sean -- on Feb 13 2011 at 22:34, you wrote:

Event All 0200 exit=105

For some reason, this event is running at varied times between
0800-0900. Do I have something wrong in the events file?

When there is no letter after the time, Binkley does strange things!

I'm sure you already know this code, but in case you've forgotten:

;Events S = Send only
; What days R = Receive only
; When to start
; When to finish
; Forced event if F showing
; Dynamic if D showing
; Mail only if M showing
; Cost = L (If cost is L means Local only) ;
C=Send to CM nodes only if C showing ;
X=No file requests sent if X showing ; N=No incoming file requests allowed if N showing ;
B=BBS Callers allowed if B showing ; K=Don't send to CM nodes if K showing ; Q=xxx
minimum size of packet to send ; H=Send Crash mail first ; E1=Exit at start of event
; E2=Exit if netmail received ;
E3=Exit if ARCmail received ;
T=X,Y #of bad calls, total ; ;Example of events:
Event All 00:00 00:00 F B L<999 E1=6 ; 1--Do MIDNITE Event All 00:00 01:00 B H Q=0 E2=25 E3=35 T=3,3 ; 2--Long distance or local All mail

Hope this helps!

Cheers... Dallas

--- timEd/386 1.10.y2k+
* Origin: The BandMaster, CANADA [telnet: bandmaster.tzo.com] (1:153/715)

Sean ..

Hello, All.

I'm having problems with a single nightly event
running at the wrong (very wrong!) time. I have but a
single EVENTS00.BBS file for the entire system which
is one dialup node and three telnet. The line in
question:

Event All 0200 exit=105

For some reason, this event is running at varied times
between 0800-0900. Do I have something wrong in the
events file?

I assume that you are running this whole deal under a .CMD file which also uses
the numeric value with a program exit to decide where in the .CMD file the logic should next go to perform the desired action.

OK .. What you can do in many cases to figure out what might be going wrong and
how programs can somehow interfere with a 'proper' logic step operation this way is somewhat simple!

You create an additional step by step mini-program action at any given generic point like this to write a discrete little file on your hard drive that has a unique text message in it. Which you can then use to trace a running .CMD or REXX file to see where a given error is being created! You give each successive
step a different pointer number, 1, 2, 3, 4 ..66 or whatever. You then use the
little program to write the message you want and that discrete unique pointer to a common trace file on your hard disk.

Then, sort of in your case, if, for example, the program doesn't exit with error level 105, as expected, but somehow is different, you can then spot exact
where to go looking for a fix.

This technique can actually be used to manually trace the whole OS/2 operating system matrix for even a massive multi program mix. Which can then tell you exactly where a given OS/2 driver or program mix may have botched even the ring
level operations that leads to a strange failure like this.

This is exactly the reason and the technique that was used for the decades I was on the official OS/2 Development Testcase crew. So that I could check all the latest driver and op system changes on my multiple OS/2 systems. Including the full multiple BBS node number mess that was and still is on the OS/2 box on
which this is being written! Which is how we found out a whole huge number of program development errors for the IBM team going all the way back to where it was in Boca Raton, Florida!

Any more thoughts needed to help you maybe?

Mike @ 1:117/100



---
* Origin: BV HUB CLL(979)696-3600 (1:117/100)

Hi Dallas,

On Mon 2039-Feb-14 02:45, Dallas Hinton (1:153/715) wrote to Sean Dennis:

For some reason, this event is running at varied times between
0800-0900. Do I have something wrong in the events file?

When there is no letter after the time, Binkley does strange things!

<hmmm> I thought he was doing this in his maximus events
instead of binkley. I was and am wondering why if he's
running binkley in front of max for his dial-up node. I'd
run this from bink.
I've never done anything with maximus events in the years
I've run it because events were always defined in
binkley.evt and once I figured it out the only thing I had
to do with max was one event that disallowed yell for chat
with sysop.


Regards,
Richard
--- timEd 1.10.y2k+
* Origin: (1:116/901)

Hi, Mike-

Thanks for the good debugging ideas, but the thing is that the event is executing properly, but at completely the wrong time! Yes, on my system, Maximus does run under a single batch file (all nodes share the same batch file
but are run independently) which does call errorlevel 105. The actual event runs completly within the original CMD file that calls the BBS.

The event itself is executing properly but for some weird reason it's running way way off-schedule and that's what I'm trying to figure out...

Thanks for the help though; anything to try to figure out what's going on here.

Later,
Sean

--- Maximus/2 3.01
* Origin: Paragon BBS - paragon.darktech.org - 423.926.7999 (1:18/200)

Hi, Richard-

<hmmm> I thought he was doing this in his maximus events
instead of binkley. I was and am wondering why if he's
running binkley in front of max for his dial-up node. I'd
run this from bink.

I'm doing this from within Maximus because I have three telnet nodes and one dialup node. I need to shut down all the nodes when I do the nightly event because I backup the current day's logs into another directory. OS/2 locks all
files in use by Maximus and no other programs can access the files unless Maximus is completely shut down.

I was under the impression that if I ran the event from EVENTS00.BBS that it would shut down all the nodes (except node 1 and I can disable that in Binkley also via BT's events) so the nightly backups could run. Not only are the nodes
not being shut down, but the event is running off of node 2 (which is the first
telnet node; all of my telnet nodes run from the WFC screen) and it's about six
to seven hours off continuiously which is what's confusing me.

Later,
Sean

--- Maximus/2 3.01
* Origin: Paragon BBS - paragon.darktech.org - 423.926.7999 (1:18/200)

Hi, Ward-

Could it be that your system has a problem with GMT-
settings which indeed provide for a 6hr or so separation?

I've got the correct settings in CONFIG.SYS for OS/2:

TZ=EST4EDT

The time is correctly set on my LAN since my pfSense (firewall/router)
box also functions as a NTP server for the LAN, but I will still take a
look at that. Just really weird that the board does this.

Later,
Sean
___
X OLXWin 1.00b X Hell hath no fury like a bureaucrat scorned.

--- Maximus/2 3.01
* Origin: Paragon BBS - paragon.darktech.org - 423.926.7999 (1:18/200)

Hi Sean -- on Feb 14 2011 at 14:40, you wrote:

I'm doing this from within Maximus because I have three telnet nodes
and one dialup node.

Ah, sorry, I leapt to a conclusion when I should have leaned gently! :-)

I ended up running Binkley in front of Max for simplicity - I couldn't get the Max event file to do what I wanted! :-) I think I wanted something too complex
for the max event, but I don't now remember what that was!



Cheers... Dallas

--- timEd/386 1.10.y2k+
* Origin: The BandMaster, CANADA [telnet: bandmaster.tzo.com] (1:153/715)

Hello, Dallas.

Monday February 14 2011 at 15:58, you wrote to me:

I ended up running Binkley in front of Max for simplicity - I couldn't
get the Max event file to do what I wanted! :-) I think I wanted something too complex for the max event, but I don't now remember what that was!

'S okay, not a problem. :) Yeah, just trying to figure out what is going on though with the event file. I will take some time this weekend to pour over the Max docs to make sure I am doing what I need to do correctly.

Later,
Sean

... Everything goes wrong all at once.
--- GoldED/2 3.0.1
* Origin: Paragon BBS - 423.926.7999 - paragon.darktech.org (1:18/200)

|-----------------|Sean Dennis wrote:

I'm having problems with a single nightly event running at
the wrong (very wrong!) time. I have but a single
EVENTS00.BBS file for the entire system which is one dialup
node and three telnet. The line in question:

|-------------------------------------|

Are you using anything like Internet Rex that can schedule events on its
own? Just curious as that is what I used to use before going back to
WINServer and using wcEvent.

... !ti tae t'nac llits uoy tub iUG eb yam ti
___
* TLX v4.10 *

--- Maximus/2 3.01
* Origin: Paragon BBS - paragon.darktech.org - 423.926.7999 (1:18/200)

Hello, Robert.

Wednesday February 16 2011 at 11:14, you wrote to me:

Are you using anything like Internet Rex that can schedule events on
its own? Just curious as that is what I used to use before going back
to WINServer and using wcEvent.

Yes, but this isn't what I need: I need Maximus to shut down /all nodes/ while
I do nightly maintenance. Max itself is supposed to do that when you use the EVENTS00.BBS file.


Later,
Sean

... I cannot live without books. - Thomas Jefferson
--- GoldED/2 3.0.1
* Origin: Paragon BBS - 423.926.7999 - paragon.darktech.org (1:18/200)

Hello Sean!

16 Feb 11 12:10, Sean Dennis wrote to Robert Wolfe:

Yes, but this isn't what I need: I need Maximus to shut down /all
nodes/ while I do nightly maintenance. Max itself is supposed to do
that when you use the EVENTS00.BBS file.

EVENTS00.BBS is intended for a single-node setup/no task number assigned. For multi-node, each node should have a unique task number, events file, log file etc. The instance that is assigned task# 1 will read EVENTS01.BBS, task#2 EVENTS02.BBS, etc. Things will probably behave when the sharing issues are resolved.

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hello, Mike.

Thursday February 17 2011 at 14:35, you wrote to me:

EVENTS00.BBS is intended for a single-node setup/no task number
assigned. For multi-node, each node should have a unique task number, events file, log file etc. The instance that is assigned task# 1 will read EVENTS01.BBS, task#2 EVENTS02.BBS, etc. Things will probably
behave when the sharing issues are resolved.

For some reason I was under the impression that EVENTS00.BBS was for all nodes,
but since that's not the case, I just need one node to actually run the event but I need all of the nodes to shut down at once. Any idea how to do that?

Later,
Sean

... Trouble is only opportunity in work clothes. - Henry J. Kaiser
--- GoldED/2 3.0.1
* Origin: Paragon BBS - 423.926.7999 - paragon.darktech.org (1:18/200)

Hi Sean -- on Feb 17 2011 at 22:39, you wrote:

For some reason I was under the impression that EVENTS00.BBS was for
all nodes, but since that's not the case, I just need one node to
actually run the event but I need all of the nodes to shut down at
once. Any idea how to do that?

I hadn't thought of that, but of course it's correct:

touch c:\flags\events00.bbs
touch c:\flags\events01.bbs
touch c:\flags\events02.bbs
touch c:\flags\events03.bbs
call Maint.bat
del c:\flags\events*.bbs


Cheers... Dallas

--- timEd/386 1.10.y2k+
* Origin: The BandMaster, CANADA [telnet: bandmaster.tzo.com] (1:153/715)

Hello, Dallas.

Friday February 18 2011 at 00:24, you wrote to me:

touch c:\flags\events00.bbs

I'm not understanding why "touching" a text file would cause Maximus to shut down each node? It's not a semaphore file...

Later,
Sean

... There's no future in time travel.
--- GoldED/2 3.0.1
* Origin: Paragon BBS - 423.926.7999 - paragon.darktech.org (1:18/200)

Hi Sean -- on Feb 18 2011 at 11:43, you wrote:

I'm not understanding why "touching" a text file would cause Maximus
to shut down each node? It's not a semaphore file...

Damn, you're right. I've GOT to stop thinking about Binkley! :-)

The docs say (as I'm sure you know):
Each node on a multinode system must have a separate events
file. However, all of the event files use the same format, so
you can simply copy a master events file to events01.bbs,
events02.bbs, and so on. (If Maximus cannot find the event
file for a specific node, it will try to read default event
information from events00.bbs, regardless of the node number
of the current session.)

So without having tried it, it should work with just one events00.bbs
file. However, have you tried just copying that file to 01, 02, etc?

It's also worth reminding you that Max must NOT be running when you
change the events*.bbs files.

Good luck!


Cheers... Dallas

--- timEd/386 1.10.y2k+
* Origin: The BandMaster, CANADA [telnet: bandmaster.tzo.com] (1:153/715)

Hello, Dallas.

Friday February 18 2011 at 14:01, you wrote to me:

So without having tried it, it should work with just one events00.bbs file. However, have you tried just copying that file to 01, 02, etc?

No, not yet, but I will...

It's also worth reminding you that Max must NOT be running when you
change the events*.bbs files.

I didn't realize that...maybe that's what the problem was.

Good luck!

Thanks. I'll try it once I can figure out how to shut down the other nodes at once but only have one node actually run the event. :)

Later,
Sean

... A hero is one who knows how to hang on one minute longer. - Norwegian proverb

--- GoldED/2 3.0.1
* Origin: Paragon BBS - 423.926.7999 - paragon.darktech.org (1:18/200)

HI SEan,

On Fri 2039-Feb-18 19:19, Sean Dennis (1:18/200) wrote to Dallas Hinton:

Thanks. I'll try it once I can figure out how to shut down the
other nodes at once but only have one node actually run the event.
:)

IN case it gets sticky here's another idea for you that
might work.

Create the event you wish to have the logs copied, it
branches to appropriate place in your 8cmd file where it
deletes a certain semaphore. NOw bear with me, because
you're going to use whatever means are at your disposal to
reboot the system, which effectively shuts down all three
nodes. Before they start up, your autoexec or equivalent
looks for that semaphore you deleted. IF found you bypass
the code which deals with your log files. If flag not
found, invoke that piece of code, slice dice and puree log
files as desired, create semaphore file.

IF something else causes an unscheduled reboot semaphore
exists, logs won't be touched until the event, which will
then cause them to be processed because at invocation of the event the semaphore is deleted.

NOt very elegant I know, but if you get stuck that might be
one cure for you.


Regards,
Richard
--- timEd 1.10.y2k+
* Origin: (1:116/901)

Another thought Sean ..

What I do to accomplish this is sort of crud but has worked for a long time here. In the .CMD or .BAT file which has the job of doing things where the other tasks are to shut up, if they can be shut up by issuing a flag of some kind to them, then what I do is start a loop in my command file at the time I need to run the event which needs to silence the other events.

I hit the top of this manual loop. It turns off task 1, 2, x and whatever. Then if goes and fires up the required maintenance task. Which is set to exit that task with an error level that the .CMD or .BAT file can see, *OR* write a little flag file on the hard disk which can become a logic part of the process.
That appears and/or dissapears as needed.

As well I also set another discrete flag file on the hard disk which, in effect, tells the whole operation that this master task is running as planned.

OK, I then include a SLEEP task at the bottom of the loop, which does not affect the running of the master task. Following that sleep exit, the .CMD or .BAT file then has a reverse direction pointer that goes back to the start of the loop in it. OK, as long as the master pointer file code is found in the loop, it just hops of to the SLEEP call and, temporarily endlessly goes around and around the loop until ..

When the master process is over, then both the error exit will be found,as well
as the process will erase the marker file that causes the loop to go loop-ti-loop! At that point, since the master .BAT or .CMD file now knows that
the critical process is finished, it sends the loop internally to restart or awaken the other tasks. And following that process, it jumps out of the master
loop to a lower point in the .BAT or .CMD file and off we go into normal work again.

The reason I use the SLEEP tool is that by doing this I don't take up a chunk of CPU time just to run romp-ity-romp around and around the loop,plus one more safety point. I have another vector enabled. If something jams up this whole process and a major event time has passed, that would tell the whole system that a jam has taken place, due again to the presence or absence of uet another
little flag file name there, I can tell the whole .BAT or .CMD file to take off
on a master fixit jump point in the whole process. Which can cure things and get the whole process going again without me being around .. except very rarely.

A long time ago my friend Paul Sittler, who wrote the very first virus that ever appeared in the original FidoNet, which we were running on 300 and 1200 baud modems at the time, taught me something! Always do everything you can to let the operating system do the work. Grin!

I've lived that way as best I can ever since. And, no, the virus deal was not deliberate! It was an accident. He wrote a CPM operating system program that figured out how I could isolate EchoMail messages to my 1:117/3000 private network addition to net 1:117 here. Then released it to all the then Fido operations. They were estatic! But he made an error. The message to each other node was a separate file on the hard disk .. or floppy. And he forgot to
erase that message/file after it went out to the next place.

In a week or so, the whole FidoNet system went down when all the servers ran out of disk space.

Chuckle. So don't forget to erase the flag points on your hard drive after you
play this cool stunt and they are no longer needed..

;)

Mike @ 117/100



---
* Origin: BV HUB CLL(979)696-3600 (1:117/100)

Hello, Mike.

Saturday February 19 2011 at 22:38, you wrote to me:

Chuckle. So don't forget to erase the flag points on your hard drive after you play this cool stunt and they are no longer needed..

What I may simply do is this: write a quickie Pascal program that monitors for the existance of a semaphore then calls up the BBS nodes to restart. It's fairly simple to do. I just have to do it. I did learn a bit though about dealing with Maximus and its events file though.

Later,
Sean

... There are people who have money and people who are rich. - Coco Chanel
--- GoldED/2 3.0.1
* Origin: Paragon BBS - 423.926.7999 - paragon.darktech.org (1:18/200)

Hello Sean!

17 Feb 11 22:39, Sean Dennis wrote to Mike Tripp:

For some reason I was under the impression that EVENTS00.BBS was for
all nodes, but since that's not the case, I just need one node to
actually run the event but I need all of the nodes to shut down at
once. Any idea how to do that?

You could have a primary node that exit with an errorlevel that points to the real work. The rest exit with another errorlevel at the same time that either quits completely (to be restarted by the primary node at the end of the work routine) or goes into infinite loop on a semaphore that is create by the primary at the start of the work and deleted by the primary at the end of the work.


.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Quoting Sean Dennis to Mike Luther on 14 Feb 111 14:33:58 <=-

Thanks for the good debugging ideas, but the thing is that the event
is executing properly, but at completely the wrong time! Yes, on my system, Maximus does run under a single batch file (all nodes share
the same batch file but are run independently) which does call
errorlevel 105. The actual event runs completly within the original
CMD file that calls the BBS.
The event itself is executing properly but for some weird reason it's running way way off-schedule and that's what I'm trying to figure
out...

Just an observation... All my Paragon packets come in GMT rather than
EST, so that might indeed be part of the problem... apparently the bbs
thinks that it is on a different time than you think it is.

ttyl neb

ps... and, yes, this is also a test message for you... ;)

... Sit down, you're rocking the boat!
--- Blue Wave/DOS v2.20
* Origin: Paragon BBS - paragon.darktech.org - 423.926.7999 (1:18/200)

Hello, Mike.

Tuesday February 22 2011 at 21:20, you wrote to me:

You could have a primary node that exit with an errorlevel that points
to the real work. The rest exit with another errorlevel at the same
time that either quits completely (to be restarted by the primary node
at the end of the work routine) or goes into infinite loop on a
semaphore that is create by the primary at the start of the work and deleted by the primary at the end of the work.

That's a good idea, thanks! I'll have to implement that.

Later,
Sean

... You're never too old to learn something new.
--- GoldED/2 3.0.1
* Origin: Paragon BBS - 423.926.7999 - paragon.darktech.org (1:18/200)

Hello, Nancy.

Tuesday February 22 2011 at 23:30, you wrote to me:

Just an observation... All my Paragon packets come in GMT rather than
EST, so that might indeed be part of the problem... apparently the bbs thinks that it is on a different time than you think it is.

Really...I never noticed that...uh, well, I'll have to check and see why that would be happening because the machine itself is set to the correct time. I wonder if it's something in the BIOS?

ps... and, yes, this is also a test message for you... ;)

So my little experiment worked then? No problems uploading or anything? (Respond to me on the board if you don't mind.)

Later,
Sean

... So often we rob tomorrow's memories by today's economies. - John Mason Brown

--- GoldED/2 3.0.1
* Origin: Paragon BBS - 423.926.7999 - paragon.darktech.org (1:18/200)

Chuckle. So don't forget to erase the flag points on your hard drive after you play this cool stunt and they are no longer needed..

What I may simply do is this: write a quickie Pascal program that
monitors for the existance of a semaphore then calls up the BBS
nodes to restart. It's fairly simple to do. I just have to do it.
I did learn a bit though about dealing with Maximus and its events
file though.

is there not a semaphore that you can write to have MAX simply exit and then catch that in a loop in the .BAT file?

another thought would be something like what i do with my FD nodes and that is that they all exit via an event with a specific errorlevel... like my suggestion above, i catch that and simply loop the .BAT file until another semaphore is removed...

trying to clarify...

my main node that does the maint exits with an errorlevel and create a maint.sem semaphore... then it loops until all of the other nodes have exited and created or removed their "i'm up" semaphore files... the other nodes then loop until the maint.sem semaphore is removed... when the main node sees that all the other nodes are down, then it runs the maint and the last thing done is
to remove the maint.sem semaphore before reloading to the top of the .BAT... all the other nodes jump to the top of the .BAT for their restart, too...

the problem may be the semaphores and exit errorlevels that you can access and catch, though...

)\/(ark


* Origin: (1:3634/12)

For some reason I was under the impression that EVENTS00.BBS was for
all nodes, but since that's not the case, I just need one node to
actually run the event but I need all of the nodes to shut down at
once. Any idea how to do that?

You could have a primary node that exit with an errorlevel that
points to the real work. The rest exit with another errorlevel at
the same time that either quits completely (to be restarted by the
primary node at the end of the work routine) or goes into infinite
loop on a semaphore that is create by the primary at the start of
the work and deleted by the primary at the end of the work.

that's what i do... you just stated it better than i ;)

)\/(ark


* Origin: (1:3634/12)

Hello mark!

26 Feb 11 11:15, mark lewis wrote to Mike Tripp:

that's what i do... you just stated it better than i ;)

:)

As much as Scott loved Vince and Binkleyterm, I'm surprised he didn't copy the concept of the forced exit flag semaphore into Maximus. It is simple to send the kill command to any chosen node in Binkley, but depending on what you're doing, you may the need the belt+suspenders you mentioned with FD to make sure that the node has detected and responded to the flag.

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hello, mark.

Saturday February 26 2011 at 11:09, you wrote to me:

the problem may be the semaphores and exit errorlevels that you can
access and catch, though...

Max simply exits via an errorlevel and that's the end of its involvement until it's called back to start again. What I've done is written a little Pascal program that will cause the node to "sleep" until the semaphore file that is specified when it's called is deleted.

Here's the program:

=== Cut ===
Program WaitFor;

Uses
SysUtils;

Begin
Repeat
SysCtrlSleep(10);
Until Not FileExists(ParamStr(1));
End.
=== Cut ===

Since all of my BBS nodes run off of a single batch file, here's the part that matters (it's called via an errorlevel exit):

=== Cut ===
:Nightly
echo . > maint.run
if %1 == 2 goto runmaint
waitfor maint.run
goto loop
:runmaint
rem ** Run Scrabble nightly maintenance
cd\doors\scrab
sdmaint 2
cd\max\drom
checkreq
cd\max
call scores.cmd 32
call scores.cmd 33
call scores.cmd 34
rem ** Purge inactive (no calls in 60 days) BBS users ***
rem muep /p
rem *** Rebuild the file base indices ***
fbp -a
del maint.run
goto Loop
=== Cut ===

"Loop" is the top of the batch file that will call each node back up. This is untested as of yet but I'll work on it later tonight hopefully.

Later,
Sean

... Experience is a good school. But the fees are high. - Heinrich Heine
--- GoldED/2 3.0.1
* Origin: Paragon BBS - 423.434.0851 - paragon.darktech.org (1:18/200)

the problem may be the semaphores and exit errorlevels that you can
access and catch, though...

Max simply exits via an errorlevel and that's the end of its
involvement until it's called back to start again.

right... what i am/was looking at was having the ability of causing it/them to exit with a specific errorlevel that can be caught and acted upon...

What I've done is written a little Pascal program that will cause
the node to "sleep" until the semaphore file that is specified
when it's called is deleted.

that should work as well as what i suggested... as long as the nodes release all files and reload them when called upon... i don't see any problems with that ;)

Here's the program:

that look svery similar to my operation over here :)

)\/(ark


* Origin: (1:3634/12)

Hello, mark.

Saturday February 26 2011 at 20:22, you wrote to me:

that look svery similar to my operation over here :)

We'll see if it works tonight. :)

Later,
Sean

... Getting ready is the secret of success. - Henry Ford
--- GoldED/2 3.0.1
* Origin: Paragon BBS - 423.434.0851 - paragon.darktech.org (1:18/200)

I'm having problems with a single nightly event running
at the wrong (very wrong!) time. I have but a single
EVENTS00.BBS file for the entire system which is one
dialup node and three telnet. The line in question:

Event All 0200 exit=105

For some reason, this event is running at varied times
between 0800-0900. Do I have something wrong in the
events file?

Are you running multiple Wait-For-Caller nodes and using the same EVENTS00.BBS file ?


--- Maximus 3.01
* Origin: Xaragmata / Adelaide SA telnet://xaragmata.mooo.com (3:800/432)

<hmmm> I thought he was doing this in his maximus events
instead of binkley. I was and am wondering why if he's
running binkley in front of max for his dial-up node. I'd
run this from bink.
I've never done anything with maximus events in the years
I've run it because events were always defined in
binkley.evt and once I figured it out the only thing I had
to do with max was one event that disallowed yell for chat
with sysop.

It is cooler to use both Binkley events and Maximus events.

Binkley events should relate to mailer stuff. Nightly BBS maintenance go in the
Maximus file. That way, a BBS computer can appear to be doing more important things than it actually is.


--- Maximus 3.01
* Origin: Xaragmata / Adelaide SA telnet://xaragmata.mooo.com (3:800/432)

Thanks for the good debugging ideas, but the thing is
that the event is executing properly, but at completely
the wrong time! Yes, on my system, Maximus does run
under a single batch file (all nodes share the same
batch file but are run independently) which does call
errorlevel 105. The actual event runs completly within
the original CMD file that calls the BBS.

The event itself is executing properly but for some
weird reason it's running way way off-schedule and
that's what I'm trying to figure out...

There's a Maximus command line option to use different event files for each node.

--- Maximus 3.01
* Origin: Xaragmata / Adelaide SA telnet://xaragmata.mooo.com (3:800/432)

I was under the impression that if I ran the event from EVENTS00.BBS that it would shut down all the nodes (except node 1 and I
can disable that in Binkley also via BT's events) so
the nightly backups could run. Not only are the nodes
not being shut down, but the event is running off of
node 2 (which is the first telnet node; all of my
telnet nodes run from the WFC screen) and it's about
six to seven hours off continuiously which is what's
confusing me.

I don't think you can share Maximus event files in this way.

If you tell 6 nodes to use the same event file, all 6 nodes will try to execute
the same thing at the same time, each in its own DOS window. Which could be causing your timing problems.

Perhaps you can try creating a semaphore so that only one node (the first node to execute the event) can run at any time. You can do this by tellign the other
batch files to return from the event immediately "if EXIST %file%" etc.

--- Maximus 3.01
* Origin: Xaragmata / Adelaide SA telnet://xaragmata.mooo.com (3:800/432)

On Sat 2039-Mar-19 01:22, Mvan Le (3:800/432) wrote to Richard Webb:

<hmmm> I thought he was doing this in his maximus events
instead of binkley. I was and am wondering why if he's
running binkley in front of max for his dial-up node. I'd
run this from bink.
I've never done anything with maximus events in the years
I've run it because events were always defined in
binkley.evt and once I figured it out the only thing I had
to do with max was one event that disallowed yell for chat
with sysop.

It is cooler to use both Binkley events and Maximus events.

Binkley events should relate to mailer stuff. Nightly BBS
maintenance go in the Maximus file. That way, a BBS computer can
appear to be doing more important things than it actually is.

Iirc a friend of mine running multinode bink/max did
something like that for maint of some games and other bbs
stuff. One node iirc was mailer the other node a wfc
maximus only. During mail periods he'd have the wfc only
node doing some bbs maintenance tasks. Horses for courses I guess <grin>. I think iirc he still did msg base maint etc. from the binkley node's events.


HOwever, it's been a few years since I recall having
anything to do with his setup, although I did help him make
the switch to bink/max initially and ad doing the co-sysop
thing from remote for him for awhil after that.

Regards,
Richard
--- timEd 1.10.y2k+
* Origin: (1:116/901)