"Tail log files" in entrypoint-user creates log spam

Open
#27 0 comments 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, shell
Domain
devops

Research direction

Start in entrypoint-user.sh at the tail -F command for ${LGSM_LOGDIR}//.log and inspect how container startup options are configured. Define a configurable way to avoid printing historical log lines, and verify that startup no longer emits unwanted log content when that option is disabled.

Written by the indexing model from the issue text.

Description

When entrypoint-user.sh executes tail -F "${LGSM_LOGDIR}"/*/*.log &, it prints out the last few lines of log content to stdout. This means if you have a large amount of game server logs, a lot of logs are sent to stdout, which is rather spammy.

Can this be configurable? I don't necessarily need or want all my historical log files, that aren't going to be changing again) to be tailed every time I start the container.

Dominant language
Shell
Stars
23
Forks
17
Avg merge
1d 1h
Merged PRs (30d)
9

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GameServerManagers/docker-linuxgsm

All issues in GameServerManagers/docker-linuxgsm

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.