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

Can the cache functionality be checked by a script? #11

Closed
JohanvdHoven opened this issue Mar 24, 2017 · 1 comment
Closed

Can the cache functionality be checked by a script? #11

JohanvdHoven opened this issue Mar 24, 2017 · 1 comment

Comments

@JohanvdHoven
Copy link

In the Steamcache guide on ARS Technica (https://arstechnica.com/gaming/2017/01/building-a-local-steam-caching-server-to-ease-the-bandwidth-blues/) there is a script on how to check if the cache functions properly.

sudo docker exec steamcache /scripts/watchlog.sh

Is a similar script available to check on the cache function in the Generic cache?

@JasonRivers
Copy link
Member

You can check the log file, located in /data/logs/access.log with:

docker exec steamcache tail -f /data/logs/access.log

It's not quite as pretty as the watchlog script currently, but we're working on some extra features for these images that will use a local version of steamdb which we've extended to have an API for our uses (the person working on that has it in his own repository at the moment as it's not ready).

The Watchlog.sh script is not hugely efficient which is why it's disabled as the default output now, This is because for each line in the log file it's spawning a few processes to colour the lines, get the depot data, etc. On a large network (around 400 users) the CPU was working quite hard just to display the log in this way. There's a python script (watchlog.py) but it's currently WIP and will be updated properly when the rest of the work is done with the local steamdb API system.

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

No branches or pull requests

2 participants