[GH-ISSUE #951] Feature Request: Backup without prompt #757

Closed
opened 2026-02-27 02:53:19 +03:00 by kerem · 13 comments
Owner

Originally created by @gjdunga on GitHub (Jul 28, 2016).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/951

Would you folks be willing to create a backup command that will skip the prompt?
Perhaps something like gameserver bn ??

Thanks!

Originally created by @gjdunga on GitHub (Jul 28, 2016). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/951 Would you folks be willing to create a backup command that will skip the prompt? Perhaps something like gameserver bn ?? Thanks!
kerem closed this issue 2026-02-27 02:53:19 +03:00
Author
Owner

@cedarlug commented on GitHub (Jul 29, 2016):

If you wish to do this using cron, see the extended discussion here:

http://steamcommunity.com/groups/linuxgsm/discussions/0/371919771743473258/

The one-liner to do what you want to do is found in this latter post:

http://steamcommunity.com/groups/linuxgsm/discussions/0/371919771743473258/?ctp=2#c364043054120014210

<!-- gh-comment-id:236064782 --> @cedarlug commented on GitHub (Jul 29, 2016): If you wish to do this using cron, see the extended discussion here: http://steamcommunity.com/groups/linuxgsm/discussions/0/371919771743473258/ The one-liner to do what you want to do is found in this latter post: http://steamcommunity.com/groups/linuxgsm/discussions/0/371919771743473258/?ctp=2#c364043054120014210
Author
Owner

@gjdunga commented on GitHub (Jul 29, 2016):

I am not using it in the cron, I'm actually using something called zip-updater that updates the Oxide plugin for RUST. I've created some functions in that program like so in bash, so that I can use the zip-updater to call lgsm to stop the server, back it up, then update it, then update oxide, and allow zip-updater to do it's own backup and restart the server..

I am not a experienced bash scripting guru. I'm learning as I go. How would you execute the echo in this instance. I am not quite sure why the backup procedure on lgsm has a confirmation prompt. I would make changes to the lgsm backup function script to skip the prompt but then any time it would be updated, I would lose those changes.

Example Code:

`fn_stop_server(){
# Stop Server
bash "${lgsmdir}"rustserver "sp"
}

fn_start_server(){
# Start server

bash "${lgsmdir}"rustserver "st"
}

fn_update_server(){
bash "${lgsmdir}"rustserver "u"
}

fn_backup_server(){
bash "${lgsmdir}"rustserver "b"
}`

<!-- gh-comment-id:236301037 --> @gjdunga commented on GitHub (Jul 29, 2016): I am not using it in the cron, I'm actually using something called zip-updater that updates the Oxide plugin for RUST. I've created some functions in that program like so in bash, so that I can use the zip-updater to call lgsm to stop the server, back it up, then update it, then update oxide, and allow zip-updater to do it's own backup and restart the server.. I am not a experienced bash scripting guru. I'm learning as I go. How would you execute the echo in this instance. I am not quite sure why the backup procedure on lgsm has a confirmation prompt. I would make changes to the lgsm backup function script to skip the prompt but then any time it would be updated, I would lose those changes. Example Code: ``` `fn_stop_server(){ # Stop Server bash "${lgsmdir}"rustserver "sp" } fn_start_server(){ # Start server bash "${lgsmdir}"rustserver "st" } fn_update_server(){ bash "${lgsmdir}"rustserver "u" } fn_backup_server(){ bash "${lgsmdir}"rustserver "b" }` ```
Author
Owner

@UltimateByte commented on GitHub (Jul 30, 2016):

@gjdunga Somebody followed my tutorial :D Glad you like the Zip Updater :p
I wish to find a way to add those functions to LGSM. :)

The backup function would need some enhancements anyways, so that you can set a backup amount to keep for example, and eventually automate an upload to a backup server.

Waiting for that, Cedar gave you the way even if you're not using cronjobs for that , here is an example:
cd /home/tsgo/ts3 && printf "yes\nno\n" |./ts3server backup >/dev/null 2>&1

<!-- gh-comment-id:236362851 --> @UltimateByte commented on GitHub (Jul 30, 2016): @gjdunga Somebody followed my tutorial :D Glad you like the Zip Updater :p I wish to find a way to add those functions to LGSM. :) The backup function would need some enhancements anyways, so that you can set a backup amount to keep for example, and eventually automate an upload to a backup server. Waiting for that, Cedar gave you the way even if you're not using cronjobs for that , here is an example: `cd /home/tsgo/ts3 && printf "yes\nno\n" |./ts3server backup >/dev/null 2>&1`
Author
Owner

@gjdunga commented on GitHub (Jul 30, 2016):

@UltimateByte , I've pondered that myself, that is combining the two. I know that when you do that, your having to do that for many games, so it's going to be a pain in the logistical arse.

BTW. Thank you for making Zip-Updater!

Please excuse my ignorance, but let's say write this as ?

fn_backup_server(){
bash cd "${lgsmdir}"&& printf "yes\nno\n" |./rustserver backup >/dev/null 2>&1 
}`

Off to go test it.. May be a few hours.. Groceries don't get themselves !!

<!-- gh-comment-id:236388672 --> @gjdunga commented on GitHub (Jul 30, 2016): @UltimateByte , I've pondered that myself, that is combining the two. I know that when you do that, your having to do that for many games, so it's going to be a pain in the logistical arse. BTW. Thank you for making Zip-Updater! Please excuse my ignorance, but let's say write this as ? ``` fn_backup_server(){ bash cd "${lgsmdir}"&& printf "yes\nno\n" |./rustserver backup >/dev/null 2>&1 }` ``` Off to go test it.. May be a few hours.. Groceries don't get themselves !!
Author
Owner

@UltimateByte commented on GitHub (Jul 30, 2016):

Yeah, i think it might work.
Where are you putting those functions by the way ? If you're using ${lgsmdir} it means you integrated it in lgsm, right ?

<!-- gh-comment-id:236395438 --> @UltimateByte commented on GitHub (Jul 30, 2016): Yeah, i think it might work. Where are you putting those functions by the way ? If you're using ${lgsmdir} it means you integrated it in lgsm, right ?
Author
Owner

@cedarlug commented on GitHub (Jul 30, 2016):

If you're running this (or invoking the function running) as the "rustserver" user and outside of cron, this shorter version would likely work just as well:
printf "yes\nno\n" | ~/rustserver backup >/dev/null 2>&1

(In the original Steam discussion, the user and the installation directory weren't LGSM defaults.)

<!-- gh-comment-id:236396159 --> @cedarlug commented on GitHub (Jul 30, 2016): If you're running this (or invoking the function running) as the "rustserver" user and outside of cron, this shorter version would likely work just as well: `printf "yes\nno\n" | ~/rustserver backup >/dev/null 2>&1` (In the original Steam discussion, the user and the installation directory weren't LGSM defaults.)
Author
Owner

@UltimateByte commented on GitHub (Jul 30, 2016):

Yeah @cedarlug that's exactly why i'm asking that. If he's within the LGSM environment, no need to cd. :)

<!-- gh-comment-id:236396462 --> @UltimateByte commented on GitHub (Jul 30, 2016): Yeah @cedarlug that's exactly why i'm asking that. If he's within the LGSM environment, no need to cd. :)
Author
Owner

@cedarlug commented on GitHub (Aug 2, 2016):

Close?

<!-- gh-comment-id:236880635 --> @cedarlug commented on GitHub (Aug 2, 2016): Close?
Author
Owner

@UltimateByte commented on GitHub (Aug 2, 2016):

Yup. We will have to have a look at the backup function at some point btw.

<!-- gh-comment-id:236887483 --> @UltimateByte commented on GitHub (Aug 2, 2016): Yup. We will have to have a look at the backup function at some point btw.
Author
Owner

@gjdunga commented on GitHub (Aug 2, 2016):

Wanted to say, that the function as I wrote it above, is working well.
@UltimateByte No, all of these changes are in zip-updater.

See full zip-updater code here:

zip-updater_beta.txt

`

<!-- gh-comment-id:236898995 --> @gjdunga commented on GitHub (Aug 2, 2016): Wanted to say, that the function as I wrote it above, is working well. @UltimateByte No, all of these changes are in zip-updater. See full zip-updater code here: [zip-updater_beta.txt](https://github.com/dgibbs64/linuxgsm/files/397057/zip-updater_beta.txt) `
Author
Owner

@gjdunga commented on GitHub (Aug 2, 2016):

I could pull lgsm and tinker to get zip-updater in there. However It would only be the rust side, I have not looked how you change code for the other games.

Gabriel

<!-- gh-comment-id:236900396 --> @gjdunga commented on GitHub (Aug 2, 2016): I could pull lgsm and tinker to get zip-updater in there. However It would only be the rust side, I have not looked how you change code for the other games. Gabriel
Author
Owner

@UltimateByte commented on GitHub (Aug 2, 2016):

Well, we'd need a smart way to implement additional functions such as this to LGSM.
It's already on its way https://github.com/dgibbs64/linuxgsm/issues/602

<!-- gh-comment-id:236906588 --> @UltimateByte commented on GitHub (Aug 2, 2016): Well, we'd need a smart way to implement additional functions such as this to LGSM. It's already on its way https://github.com/dgibbs64/linuxgsm/issues/602
Author
Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

<!-- gh-comment-id:406188670 --> @lock[bot] commented on GitHub (Jul 19, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Sign in to join this conversation.
No labels
Atomic
Epic
cannot reproduce
command: backup
command: console
command: debug
command: details
command: fast-dl
command: install
command: mods
command: monitor
command: post-details
command: restart
command: send
command: start
command: stop
command: update
command: update-lgsm
command: validate
command: wipe
distro: AlmaLinux
distro: Arch Linux
distro: CentOS
distro: Debian
distro: Fedora
distro: RedHat
distro: Rocky Linux
distro: Ubuntu
distro: openSUSE
engine: goldsrc
engine: source
game: 7 Days to Die
game: ARMA 3
game: Ark: Survival Evolved
game: Assetto Corsa
game: Avorion
game: BATTALION: Legacy
game: Barotrauma
game: Battalion 1944
game: Battlefield 1942
game: Black Mesa: Deathmatch
game: Blade Symphony
game: Call of Duty 2
game: Call of Duty 4
game: Call of Duty: United Offensive
game: Counter-Strike 1.6
game: Counter-Strike 2
game: Counter-Strike: Global Offensive
game: Counter-Strike: Source
game: Day of Infamy
game: Dayz
game: Death Match Classic
game: Don't Starve Together
game: ET: Legacy
game: Eco
game: Factorio
game: Factorio
game: Garry's Mod
game: Half-Life
game: Hurtword
game: Insurgecy
game: Insurgecy
game: Insurgency: Sandstorm
game: Just Cause 3
game: Killing Floor
game: Killing Floor 2
game: Left 4 Dead 2
game: Minecraft
game: Minecraft Bedrock
game: Mordhau
game: Multi Theft Auto
game: Mumble
game: Natural Selection 2
game: No More Room in Hell
game: Pavlov VR
game: Post Scriptum
game: Project Zomboid
game: Quake 3
game: QuakeWorld
game: Red Orchestra: Ostfront 41-45
game: Return to Castle Wolfenstein
game: Rising World
game: Rust
game: San Andreas Multiplayer
game: Satisfactory
game: Soldat
game: Soldier of Fortune 2
game: Squad
game: Squad 44
game: Starbound
game: Stationeers
game: Sven Co-op
game: Team Fortress 2
game: Teamspeak 3
game: Teeworlds
game: Terraria
game: The Front
game: Unreal Tournament 2004
game: Unreal Tournament 3
game: Unreal Tournament 99
game: Unturned
game: Valheim
game: Wurm Unlimited
game: Zombie Master Reborn
game: label missing
good first issue
help wanted
info: alerts
info: dependency
info: docker
info: docs
info: email
info: query
info: steamcmd
info: systemd
info: tmux
info: website
info: website
needs more info
outcome: duplicate
outcome: issue resolved
outcome: issue resolved
outcome: issue unresolved
outcome: pr accepted
outcome: pr rejected
outcome: unconfirmed
outcome: wontfix
outcome: wrong forum
potential-duplicate
priority
pull-request
type: bug
type: feature
type: feature
type: feature request
type: game server request
type: refactor
waiting response
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/LinuxGSM#757
No description provided.