Nemrun for SteamCMD Linux
2 Attachment(s)
So, a few people have been bugging me to release my updated version of Nemrun for SteamCMD... so here it is.
This is based on Nemrun 1.8.7. The new (required) parameters are actually the same ones the server uses with its newer -autoupdate support: -steam_dir - The directory steamcmd lives in. Replaces -steamdir which was for hldsupdatetool. -steamcmd_script - The steamcmd script to run. Relative paths are treated as relative from the steam_dir. Note: This includes srcdsupdatecheck from Nemrun 1.8.7. Edit: I wonder if the reason Nephyrin didn't update this for SteamCMD himself is because he now works for Valve. |
Re: Nemrun for SteamCMD Linux
Thanks. :bacon!:
|
Re: Nemrun for SteamCMD Linux
Quote:
|
Re: Nemrun for SteamCMD Linux
Does anyone have any clue why SteamCMD won't update steam.inf on my servers? (That's plural, it's happening on all three systems). steam.inf won't update with the new version number so nemrun never restarts the servers to update.
|
Re: Nemrun for SteamCMD Linux
Quote:
|
Re: Nemrun for SteamCMD Linux
I just realized that I never gave my solution...
SteamCMD wasn't updating my steam.inf file so nemrun never thought the server was fully updated. To fix it, I had to switch my user-relative path (~/tfserver) to an absolute path (/home/user/tfserver). |
Re: Nemrun for SteamCMD Linux
Two things:
I just noticed the first post had the command listed as -steamcmd_runscript. It's actually -steamcmd_script. I also want to post the command lines I use with nemrun_steamcmd to give people an idea of how it works, at least if you use it in its update daemon mode. For TF2, my update daemon is running like this: Code:
#!/bin/bash Code:
#!/bin/bash |
Re: Nemrun for SteamCMD Linux
Is this still supported (meaning does it work) and err does it have all the features that the original Nemrun with running multiple servers off 1 installation and auto updating...?
|
Re: Nemrun for SteamCMD Linux
Hi,
where is emailTheAdmins.sh and notifyadmins.sh? |
Re: Nemrun for SteamCMD Linux
Quote:
Quote:
There are reasons for this... 1. notifyadmins.sh doesn't specify how to contact the admins. 2. emailTheAdmins.sh would need to be written differently depending on how your server is set up... if it has a sendmail binary (installed by most mail servers) it could use that, but otherwise it'd have to talk SMTP directly with a remote mail server. Also, just because it has a .sh extension doesn't strictly mean it's a shell script... it could be written in perl or python and passed the perl/python interpreter on the first line (the shebang line). |
All times are GMT -4. The time now is 15:42. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.