[GH-ISSUE #2930] Blacklist log directores from getting log purged #2090

Closed
opened 2026-02-27 03:00:48 +03:00 by kerem · 3 comments
Owner

Originally created by @godrider on GitHub (Jun 17, 2020).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2930

User Story

As a server administrator, I want be able to choose and blacklist log directories from getting log purged.

Basic info

  • Distro: [Debian 10]
  • Game: [Multiple]
  • Function: [Logging]
  • LinuxGSM version: [v20.3.3]

Further Information

Similarly to this, I want to prevent certain log directories from getting log purged after log files older than X days will be automatically deleted. This new feature prevents important data, residing in these directories, from getting deleted out of the user's hands. Think of chat logs, plugin error information, general plugin information.

Example:

## Logging | https://docs.linuxgsm.com/features/logging
consolelogging="on"
logdays="7"
# Do not delete logs from the following directories
blacklist="${commonsourcelogs}; ${sourcemodlogdir}"

The commonsourcelogs and sourcemodlogdir variables are references to the logpaths written in core_log.sh.

Possible Solution

Loop through the user defined blacklist array and check in core_log.sh which directories will be scanned for file deletion.

Originally created by @godrider on GitHub (Jun 17, 2020). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2930 ## User Story As a server administrator, I want be able to choose and blacklist log directories from getting log purged. ## Basic info * **Distro:** [Debian 10] * **Game:** [Multiple] * **Function:** [Logging] * **LinuxGSM version:** [v20.3.3] ## Further Information Similarly to [this](https://github.com/GameServerManagers/LinuxGSM/issues/2304#issue-436951410), I want to prevent certain log directories from getting log purged after log files older than X days will be automatically deleted. This new feature prevents important data, residing in these directories, from getting deleted out of the user's hands. Think of chat logs, plugin error information, general plugin information. Example: ``` ## Logging | https://docs.linuxgsm.com/features/logging consolelogging="on" logdays="7" # Do not delete logs from the following directories blacklist="${commonsourcelogs}; ${sourcemodlogdir}" ``` The commonsourcelogs and sourcemodlogdir variables are references to the logpaths written in `core_log.sh`. ## Possible Solution Loop through the user defined blacklist array and check in `core_log.sh` which directories will be scanned for file deletion.
kerem 2026-02-27 03:00:48 +03:00
Author
Owner

@issue-label-bot[bot] commented on GitHub (Jun 17, 2020):

Issue-Label Bot is automatically applying the label type: feature request to this issue, with a confidence of 0.98. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

<!-- gh-comment-id:645099803 --> @issue-label-bot[bot] commented on GitHub (Jun 17, 2020): Issue-Label Bot is automatically applying the label `type: feature request` to this issue, with a confidence of 0.98. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: [app homepage](https://github.com/marketplace/issue-label-bot), [dashboard](https://mlbot.net/data/GameServerManagers/LinuxGSM) and [code](https://github.com/hamelsmu/MLapp) for this bot.
Author
Owner

@dgibbs64 commented on GitHub (Jul 9, 2020):

Clearing of logs was added as the log files built up so much that it overloaded some game servers. I don't recommend keeping logs and they should be cleared down after a time. This is standard procedure of Linux logs as well. I recommend setting the log rotation to 30 days if you need to retain them for longer. If you still need them for the long term auditing purposes you should create a backup archive of the logs.

<!-- gh-comment-id:655996159 --> @dgibbs64 commented on GitHub (Jul 9, 2020): Clearing of logs was added as the log files built up so much that it overloaded some game servers. I don't recommend keeping logs and they should be cleared down after a time. This is standard procedure of Linux logs as well. I recommend setting the log rotation to 30 days if you need to retain them for longer. If you still need them for the long term auditing purposes you should create a backup archive of the logs.
Author
Owner

@github-actions[bot] commented on GitHub (Jul 10, 2021):

This issue 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:877515374 --> @github-actions[bot] commented on GitHub (Jul 10, 2021): This issue 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#2090
No description provided.