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

Verify Logging #4

Open
JustinBenedick opened this issue Jun 3, 2018 · 1 comment
Open

Verify Logging #4

JustinBenedick opened this issue Jun 3, 2018 · 1 comment

Comments

@JustinBenedick
Copy link
Member

@JustinBenedick:
Does this stock server create and use log files?

Determine if the stock (as in zero config changes) version of this server creates log files. If this image doesn't create log files you may have to do this testing on a stock server outside of Docker.
If no

comment that it doesn't close this issue and skip remaining steps.
If yes

Let me know (via comments on this issue):

if this docker image properly creates / use the log files.
    if it doesn't @dudleycodes will fix the issue
the directory (full path) log files are created in.
the default naming scheme of the log file
    so that @dudleycodes can create tests that checks for creation/usage of log files.
@JustinBenedick
Copy link
Member Author

Docker is only saving log files in /app/hl1mp/addons/sourcemod/logs and not saving log files in /app/hl1mp/logs.

Did test in VM and confirmed log files were saved in
/home/sysoper/gameserver/hl1mp/addons/sourcemod/logs
accelerator.log
errors_20180603.log
L20180603.log
STEAMID_03_Jun_2018.txt

/home/sysoper/gameserver/hl1mp/logs
l0603000.log
l0603001.log
l0603002.log
l0603003.log
l0603004.log

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

No branches or pull requests

1 participant