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..
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.
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.
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.
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?
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...
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!
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.
:)
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.
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 ;)
the problem may be the semaphores and exit errorlevels that you can
access and catch, though...
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:
that look svery similar to my operation over here :)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,042 |
Nodes: | 15 (0 / 15) |
Uptime: | 145:00:34 |
Calls: | 500,263 |
Calls today: | 1 |
Files: | 95,201 |
D/L today: |
120 files (65,847K bytes) |
Messages: | 464,629 |