Does Mystic have, hard coded an environment veriable for node number...
ie wildcat is %wcnodeid% or Synchronet is %sbbsnnum%... Is there one internal to Mystic. I know I can create one with a batch file...is
there one the BBS make with its own startup process
Does Mystic have, hard coded an environment veriable for node number. ie wildcat is %wcnodeid% or Synchronet is %sbbsnnum%... Is there one internal to Mystic. I know I can create one with a batch file...is there one the BBS make with its own startup process
%3
Okay... read the doc a little...
if I were to write a batch file, not saying I am, I'm just saying...
:start
cd\bbs\node%wcnodeid%\
c:\bbs\stuff\something.exe config.%wcnodeid%
:Stop
Batch file would run, and if the user was on node 3, it would change
the user to the directory \bbs\bode3\ and exicute an exe the
something.exe file with config.3 bedide it....
ergo,
:start
cd\bbs\node%%3%
c:\bbs\stuff\something.exe config.%%3%
:stop
I am not sure if I explained myself correctly...
I'm looking for environmet variables that I can pull up in a batch
file. This might be a parameter that sends out the node number...
good enough... I can add some lines in a batch file if need be and
create my own.
I don't even think this could be done with any BBS software unless you actually pass that node number to the batch file from the BBS itself.
I don't even think this could be done with any BBS software
unless you actually pass that node number to the batch file from
the BBS itself.
I just mentioned 2 BBS software that do it
Start:
During operation, Synchronet may write to several different
environment variables which can be utilized by other programs. Some
of these environment variables are also used by the utility programs
that are included with Synchronet as well as third party programs
written for Synchronet. Following is a list of environment variables
and a brief explanation of them:
WINServer AKA WildCat 5 does the same thing. It generates WCNODEID as
an environment variable when it spawns a window to run a door...
The answer is no, or it sounds like it... no big because I can make
one up in the batch file as needed.
...
set nodenum=%3
cd\bbs\node%nodenum%
...
Just asking
My question was does it do it automaticly or not... it was a yes or no question.
Answer is no, you'll have to do them on the fly...
But thanx
My question was does it do it automaticly or not... it was a yes or
no question.
Answer is no, you'll have to do them on the fly...
How is the answer no? When you execute the batch file from your events
you pass the node parameter (%3). What more do you want!?!?
I simply wanted to know if mystic created it automaticly. Like it does
in a few other packages.
The answer was no it doesn't.
Relax... Mystic is good....
i think the key word here is "automatic"... you have to specifically
put "%3" in the data line to pass the node number... that's not "automatic"... i suspect the OP was looking for an already existing environment variable like %MYSTICNODE% similar to %WCNODE%... in the
case of %WCNODE%, the BBS creates it in the spawned shell where the
door script is executed... in this case, "%3" wouldn't need to be
passed at all since the value should be the same as %MYSTICNODE% if it existed...
As for %WCNODE%, does that not need to be configured to do so at some
Either package does not require the sysop to do anything.
--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
No I was not referring to an OS in my original question...
I currently run the Linux Raspberyy Pi version of Mystic and been a
good experience.
IS there some easy way to be notified if someone uses a feature on the BBS... For example... If a new user creates a new account the SysOp is sent a message informing them that this has happened.
Can something be done like that if/when a menu option has been
triggered??
IS there some easy way to be notified if someone uses a feature on the BBS... For example... If a new user creates a new account the SysOp is sent a message informing them that this has happened.
IS there some easy way to be notified if someone uses a feature on th BBS... For example... If a new user creates a new account the SysOp i sent a message informing them that this has happened.
Yes you can do this is many ways.
Specifically for new users, Mystic already does this automatically for
you as long as you have "sysletter.txt" in the data directory and you
have the "Feedback To" field in the System Configuration set to your
user name.
You will get an email whenever a new account is created.
Default installations of Mystic do include a sysletter.txt by default so if you are not seeing this happen, check to make sure it exists and that your Sysop names and Feedback To names are configured.
I would like to thank you for your response... I read over my initial message and I see where the source of confusion is.... I'll try to
explain myself a little better.
I would like to be notified when someone presses a menu feature... LIKE when a New User registers as a user. For example I can be notified
every time someone access a specific Door or whatever..
In the "Data" field set it to:
runlord.txt;1;Mystic BBS;IB Joe;LORD has been executed
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,044 |
Nodes: | 15 (0 / 15) |
Uptime: | 52:24:24 |
Calls: | 236,098 |
Files: | 60,370 |
D/L today: |
43 files (38,067K bytes) |
Messages: | 289,236 |