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.

Sign up for GitHub

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

Jump to bottom

MVDSV not started when running script from cronjob #19

Closed
liback opened this issue Mar 20, 2018 · 1 comment
Closed

MVDSV not started when running script from cronjob #19

liback opened this issue Mar 20, 2018 · 1 comment
Labels
bug resolved
Milestone
1.8

Comments

@liback
Copy link
Contributor

liback commented Mar 20, 2018 •
edited
Loading

QTV and QWFWD are started but not all the MVDSV ports when running start_servers from cronjob. Incorrect work dir as the MVDSV start scripts are using scriptfolder variable instead of installation dir for the path.
@liback liback added the bug label Mar 20, 2018
@liback liback added this to the 1.8 milestone Mar 20, 2018
liback added a commit that referenced this issue Mar 20, 2018
@liback
Fix cronjob script execution (#19)
e232609
@liback
Copy link
Contributor Author

liback commented Mar 20, 2018 •
edited
Loading

Script was executed from user home dir (instead of real nquakesv installation dir) which start_servers then used to try to launch MVDSV. Instead of changing start_servers (maybe there is some good reason it is like it is...) we're now setting nquakesv to the current dir before running start_servers in cronjob.

Also a user definition was missing in the cronjob.

@liback liback closed this as completed Mar 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug resolved
Projects
None yet
Milestone
1.8
Development

No branches or pull requests
1 participant
@liback