Search results

That's completely fine with me. Would you say that it might be worth a try to create a feature request on the code repo?

First of all thank you for responding and getting into this topic with me. (y) It's just a script, running in a specific interval (1min for example) reading the .rtreports stats. Doesn't matter the load or anything else. It gives us an idea of how many connections OLS receives. Similar to...

The .rtreport files obviously contain the access statistics of OLS (https://docs.litespeedtech.com/lsws/realtime/#through-rtreport-files). Our monitoring reads these files to generate aggregated statistics and creates graphs from it, etc. Our monitoring services and scripts don't run as root...

> I'm not sure if you know what you're doing. :ROFLMAO: Our monitoring reads the .rtreport files from /dev/shm/ols. But the permissions of /dev/shm/ols always gets reset to a default permission (0750), where only the user and group, under which OLS is running, is able to access these files...

I see that this is triggered automatically when the QUIC.cloud whitelist was changed: 2025-03-05 09:38:27.029847 [INFO] [1499525] Daily download QUIC.cloud whitelist IP to tmp/download-quic-cloud-ips ... 2025-03-05 09:38:27.661524 [NOTICE] [1499525] QUIC.cloud IP list has been changed, request...

Update: Looks as if this is hard-coded in the OLS code? https://github.com/litespeedtech/openlitespeed/blob/75f22e088a117a971f8c39543d3aacb4903491ad/src/main/httpserver.cpp#L2692

Hello folks, We're monitoring the OLS setups by frequently parsing the .rtreport files located in /dev/shm/ols/status. Initially the permissions on /dev/shm/ols are set to 750 with owner and group set to the ones defined in the OLS config (httpd_config). We've changed the permissions so that...