Native Linux server (with management scripts)

hello Alloc, I am getting this error message:

-bash: sel: command not found

-bash: sel: command not found

-bash: sel: command not found

Telnet not enabled or no password set.

My server is Debian 7

 
Last edited by a moderator:
H3llghost is almost right ... the first character being a shebang of course ... ;)
Code:
#!/bin/sh
. /usr/local/lib/7dtd/common.sh

telnetCommand $1 "say Hello to $4"

hello Alloc, I am getting this error message:
-bash: sel: command not found

-bash: sel: command not found

-bash: sel: command not found

Telnet not enabled or no password set.

My server is Debian 7
Hmz, should really update this part of the scripts ...

Try this:

Code:
#!/bin/sh
. /usr/local/lib/7dtd/common.sh
checkRootLoadConf

telnetCommand $1 "say Hello to $4"
 
No longer does the error message, however also not receive the welcome message when I enter the server.

Look print attached, is correct?



 
Ah, sorry, there's an error in the documentation. All hooks go to a folder called "hooks" in SDTD_BASE.

So the path for the hook should be:

Code:
/home/sdtd/hooks/playerConnect/bemVindo.sh
Also in your screenshot it looks like there's an empty line before the shebang which should not be the case (even though this probably won't cause a problem).

 
Touch does set the exec-flag on a file, it only changes the modification time. You have to run chmod +x filename.sh to make it executable.

 
Hm, ok ... will run a test myself in a few minutes, but it really should work ... ;)

 
Just noticed you put /bin/sh in the shebang ... Please try it with /bin/bash as quite a lot of things in the scripts require a bash.

 
Seconds ;)

You don't want the script to block for hours or even minutes. Should never be greater than like 3sec. And only be required for stuff like entity querying as you have to wait for the output to be complete before killing the connection.

 
hello friend, I'm getting this error message.

/home/sdtd/instances/brasil/players.xml:6.112: Attribute nick redefineddo" playtime="0" logins="1" lastlogin="xxxxxxxx" online="true" entityid="5982"

^

/home/sdtd/instances/brasil/players.xml:6.112: Attribute playtime redefined

do" playtime="0" logins="1" lastlogin="xxxxxxx" online="true" entityid="5982"

^

/home/sdtd/instances/brasil/players.xml:6.112: Attribute logins redefined

do" playtime="0" logins="1" lastlogin="xxxxxxx" online="true" entityid="5982"

^

/home/sdtd/instances/brasil/players.xml:6.112: Attribute lastlogin redefined

do" playtime="0" logins="1" lastlogin="xxxxxx" online="true" entityid="5982"

^

/home/sdtd/instances/brasil/players.xml:6.112: Attribute online redefined

do" playtime="0" logins="1" lastlogin="xxxxxxx" online="true" entityid="5982"

^

/home/sdtd/instances/brasil/players.xml:6.112: Attribute entityid redefined

do" playtime="0" logins="1" lastlogin="xxxxxxx" online="true" entityid="5982"

Question 2: and when I use the command "7dtd.sh kill myinstance" and "7dtd.sh start myinstance" the days of the game back to zero.

 
Hm, might be the same problem as I saw before ... I assume you are using a version of the scripts prior to v.22? If so please update and delete the players.xml (or at least clean it up manually).

Might also be related to the Telnet thread having crashed. Will try to add some checks in there.

/EDIT: Nope, should not be a problem ;)

Regarding Q2: I think this only happens when the Telnet thread crashed so shutdown does not work. Can't do anything about it as that's a bug in the game itself.

 
Last edited by a moderator:
Regarding Q2: I think this only happens when the Telnet thread crashed so shutdown does not work. Can't do anything about it as that's a bug in the game itself.
It is an issue with the telnet thread, the kill uses normally the shutdown command. The "work-around" is to use the shutdown via console as player.

It should be fixed on server side, when the kill signal is send to save the day too. But at the moment remember the day and set it manually or shutdown the server when you are connected to the server via console and killing all monitor-log.sh after it.

 
Back
Top