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

left over LOCKs on system reboot #57

Open
BananaAcid opened this issue Apr 9, 2024 · 3 comments
Open

left over LOCKs on system reboot #57

BananaAcid opened this issue Apr 9, 2024 · 3 comments

Comments

@BananaAcid
Copy link
Contributor

Sometimes my server crashes or a windows update got forced through.

I added a scheduler task to remove all .\servers*.LOCK files on system start.

Maybe, this could be added by default (when creating the game scheduler task)

@patrix87
Copy link
Owner

Yes, this could prevent some issues.
Please open a PR

@omayhemo
Copy link

I was flummoxed on why the server wouldn't start. The cmd window just disappears, you should be pipping output to it and leaving it to keypress for exit, so we can see what's going on. I'm not sure I understand why the lock management is so messy, perhaps it's because there support for so many different games?

@patrix87
Copy link
Owner

Enable DEBUG mode in the config if you want the window to stay open.
The lock system is there to prevent a state where the server hangs or takes a while to start and then another task start and try to run the server again creating a run away that would impact the performance of the other servers.

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

No branches or pull requests

3 participants