Is anyone getting a "UNable to find mystic.dat" error?
If I run mystic -cfg from any directory other than the /opt/mystic, I
get the error. I see it was a resolved a few versions back so wondering if I need to export a variable ($PATH includes /opt/mystic) or if it is
an OS issue??
Is anyone getting a "UNable to find mystic.dat" error?
If I run mystic -cfg from any directory other than the /opt/mystic, I get the error. I see it was a resolved a few versions back so wondering if I need to export a variable ($PATH includes /opt/mystic) or if it is an OS issue??
Is anyone getting a "UNable to find mystic.dat" error?
If I run mystic -cfg from any directory other than the /opt/mystic, I get the error. I see it was a resolved a few versions back so wondering if I need to export a variable ($PATH includes /opt/mystic) or if it is an OS issue??
On 2018 May 20 00:30:46, you wrote to All:
Is anyone getting a "UNable to find mystic.dat" error?
If I run mystic -cfg from any directory other than the /opt/mystic, I
get the error. I see it was a resolved a few versions back so
wondering if I need to export a variable ($PATH includes /opt/mystic)
or if it is an OS issue??
IIRC, you have to be in the dir where the file exists or you have to
set an environment variable pointing to that directory...
)\/(ark
Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Format that brain @FN@, it's warped I tell you!
-+-
+ Origin: (1:3634/12.73)
If I run mystic -cfg from any directory other than the /opt/mystic,
I get the error. I see it was a resolved a few versions back so
wondering if I need to export a variable ($PATH includes
/opt/mystic) or if it is an OS issue??
IIRC, you have to be in the dir where the file exists or you have to
set an environment variable pointing to that directory...
Do you remember what the exact variable is?
On 2018 May 20 21:24:04, you wrote to me:While the software is outstanding, the documentation is a bit outdated. But, there are enough hints to find what one is looking for, if I stop & read the obvious...
If I run mystic -cfg from any directory other than the /opt/mystic,
I get the error. I see it was a resolved a few versions back so
wondering if I need to export a variable ($PATH includes
/opt/mystic) or if it is an OS issue??
IIRC, you have to be in the dir where the file exists or you have to
set an environment variable pointing to that directory...
When the servers are started, "mis -d" Mystic defines the expected env variableDo you remember what the exact variable is?
i do not and T isn't here to ask if she remembers... however, i went snooping on her box and she has a script for running mystic and the config stuff...
#~/bin/bash
CWD=$PWD
echo -e "\033%@" && echo -e "\033(U"
cd ~/bbs
./mystic -cfg
cd $CWD
reset
#~/bin/bash
CWD=$PWD
echo -e "\033%@" && echo -e "\033(U"
cd ~/bbs
~/bbs/mis
cd $CWD
reset
i'm not sure what was being done here but it looks like someone was testing the bbs variable... however, they still changed into the bbs directory instead of running from where they were...
#~/bin/bash
CWD=$PWD
echo -e "\033%@" && echo -e "\033(U"
#echo -e "\033%G"
echo \"$MYSTICBBS\"
MYSTICBBS=~/bbs
export MYSTICBBS
echo \"$MYSTICBBS\"
echo "--------------------"
set | egrep -i -e "mystic"
echo "--------------------"
read -p "hit ENTER to continue"
cd ~/bbs
~/bbs/nodespy
cd $CWD
reset
)\/(ark
Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... It's hard to believe he beat out 1,000,000 other sperm.
-+-
+ Origin: (1:3634/12.73)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,037 |
Nodes: | 15 (1 / 14) |
Uptime: | 00:14:48 |
Calls: | 10 |
Calls today: | 10 |
Files: | 95,181 |
D/L today: |
14,303 files (1,905M bytes) |
Messages: | 465,484 |