Beiträge von Dennis
-
-
A new update has been released to introduce support for Call of Duty 5.
Some minor bugs were fixed, random mapcycle was reintroduced and the config files
have been changed to .json format - you need to reconfigure! Be careful, as it does
not allow mistakes in syntax. If you need help with the new syntax, open a thread. -
Minimum Version is 5.4.
-
Uncomment "extension=php_mbstring.dll" in php.ini.
-
The Path to your logfile is wrong, when commands are not recognized.
-
Then your GUID is not the same as the one you have written in users.cfg.
-
You need to install PHP to run ManuAdminMod, you can find insturctions in our documentation.
-
I'm glad it helps you. But i'm pretty "Wat?" why it does so.
-
Lawl. Just lawl. -dmS is perfectly valid and there should be no need to give the params one for one.
-
That's correct. Show shows the log. MAM seems to run fine.
As long as MAM runs, everything is okay. There is no output with .daemon.sh,
and there is only was started as output for mam.sh start.Where is the problem, then?
-
We wanted to know what happens if you do ./daemon.sh after setting its chmod u+x and what is the output of ./mam.sh show after you did ./mam.sh start.
This log is absolutley irrelevant to the questions. -
What happens when executing .daemon.sh after setting chmod u+x on it?
-
Banlists are not managed by MAM. You would need to symlink the banlist files of your servers.
Zitatc:\>mklink "C:\Link.xyz" "D:\RealFile.xyz"
-
No. You would need to specify seperate Config & Log DIRECTORIES, but there would be still 8 instances of MAM using the same folders but config and logs.
You could share your banlist between all servers by symlinking them, for example. -
That should absoluteley not be needed. It works fine on our test installations, there must be an error in your system or a mistake.
-
./mam.sh start does nothing else as executing .daemon.sh.
Is screen -dmS name daemon.sh working? -
Screen installed? What error do you have when you directly execute .daemon.sh? Permissions set?
-
-
Try to execute .daemon.sh and see what errors it reports.
Maybe you need to change "# !/bin/bash" to "#!/bin/bash" (Delete Space!)
-
Which error did you get? Which OS?
