Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Unexpected EOF in info_game.sh #4482

Closed
dragokas opened this issue Feb 4, 2024 · 5 comments
Closed

[Bug]: Unexpected EOF in info_game.sh #4482

dragokas opened this issue Feb 4, 2024 · 5 comments

Comments

@dragokas
Copy link

dragokas commented Feb 4, 2024

User story

Unexpected EOF error is raised when you try to restart the server

Game

Left 4 Dead 1

Linux distro

Debian 12

Command

command: restart

Further information

Unexpected EOF error is raised when you try to start, stop or restart the server.
update-lgsm doesn't help. All modules are up to date.

Relevant log output

l4dmain@debian10x64:~$ ./l4dserver r
/home/l4dmain/lgsm/modules/info_game.sh: eval: line 184: unexpected EOF while looking for matching `"'

Steps to reproduce

Execute:

./l4dserver r
@dragokas
Copy link
Author

dragokas commented Feb 4, 2024

Ok, figured out. It doesn't like character sequnce

$(

in rcon_password

@h3o66
Copy link
Member

h3o66 commented Feb 4, 2024

you can probably use this if you put this in single quotes like this:

variable='a$(b'

@h3o66 h3o66 closed this as completed Feb 4, 2024
@github-project-automation github-project-automation bot moved this from 🆕 New Issues to ✅ Done in LinuxGSM Backlog Feb 4, 2024
@dragokas
Copy link
Author

dragokas commented Feb 4, 2024

Not agree it is solved. It's better to insert somewhere a meaningful message saying that it is forbidden to use $( sequence in the password instead of throwing a syntax error.

@h3o66
Copy link
Member

h3o66 commented Feb 4, 2024

well, this is a standard open sequence for a subprocess in bash.

Did you at least check my comment ?
That works for me to have a $( in the variable

I do only see a way to stop lgsm when it detects a not "working" config.
To check for the string might not be not be the best idea, better only validate the read of the configs.

@dragokas
Copy link
Author

dragokas commented Feb 4, 2024

I'm not the only one. Other people may also suffer similar issue. Fix should go to master branch, not to my own local script. However, you closed this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants