starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #1994] Part of check_permissions extremely slow #1565

New issue

Closed

opened 2026-02-27 02:57:51 +03:00 by kerem · 7 comments

kerem commented

2026-02-27 02:57:51 +03:00

Owner

Originally created by @Donkie on GitHub (Aug 28, 2018).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1994

Describe the bug
Running most commands take next to forever (multiple minutes sometimes) for me on my Ubuntu 14.04 server with a HDD drive. I've analyzed the issue using iotop and found that a process with the command 'find "/my/server/files" -not -user steam' occupies a whole lot of I/O usage. This HDD drive is rather slow I've found, and I got quite some files in said folder, but that shouldn't affect the performance of just starting the server.

The culprit code is found at github.com/GameServerManagers/LinuxGSM@0276b943e3/lgsm/functions/check_permissions.sh (L21-L25)
which, from my knowledge, tries to look through every single file in that folder and make sure the permissions are set correctly? Why is this necessary?

To Reproduce
Steps to reproduce the behaviour:

Have a slow drive
Have many files in your server files directory
Run any LGSM command

Expected behaviour
That the command was fast and smooth

** Minimum Information **
Game server: Garry's Mod
https://hastebin.com/onufenuvox

Additional context

Originally created by @Donkie on GitHub (Aug 28, 2018). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1994 **Describe the bug** Running most commands take next to forever (multiple minutes sometimes) for me on my Ubuntu 14.04 server with a HDD drive. I've analyzed the issue using iotop and found that a process with the command 'find "/my/server/files" -not -user steam' occupies a whole lot of I/O usage. This HDD drive is rather slow I've found, and I got quite some files in said folder, but that shouldn't affect the performance of just starting the server. The culprit code is found at https://github.com/GameServerManagers/LinuxGSM/blob/0276b943e37293b68f3dbc2aca4e6f57fa39073b/lgsm/functions/check_permissions.sh#L21-L25 which, from my knowledge, tries to look through every single file in that folder and make sure the permissions are set correctly? Why is this necessary? **To Reproduce** Steps to reproduce the behaviour: 1. Have a slow drive 2. Have many files in your server files directory 3. Run any LGSM command **Expected behaviour** That the command was fast and smooth ** Minimum Information ** Game server: Garry's Mod https://hastebin.com/onufenuvox **Additional context**

kerem

2026-02-27 02:57:51 +03:00

closed this issue
added the
outcome: wontfix
label

kerem commented

2026-02-27 02:57:51 +03:00

Author

Owner

@Donkie commented on GitHub (Aug 28, 2018):

After some additional research I found that this is partially my fault, an addon I had installed had created ~36,000 folders with logs which took some times to look through. However, I still don't think such a case should affect the performance of this program.

@Donkie commented on GitHub (Aug 28, 2018): After some additional research I found that this is partially my fault, an addon I had installed had created ~36,000 folders with logs which took some times to look through. However, I still don't think such a case should affect the performance of this program.

kerem commented

2026-02-27 02:57:51 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Aug 28, 2018):

The permissions check normally takes less than a second to run. This is definitely the fault of the addon creating an extremely excessive number of files and dirs. So I would expect the find command to take a long time to get through all that.

So im not sure how you can think that having 36,000 dir's to scan shouldn't affect the performance of LinuxGSM.

What is the addon you are using? as there are checks for some gmod logs in LinuxGSM to clear them after x days

@dgibbs64 commented on GitHub (Aug 28, 2018): The permissions check normally takes less than a second to run. This is definitely the fault of the addon creating an extremely excessive number of files and dirs. So I would expect the `find` command to take a long time to get through all that. So im not sure how you can think that having 36,000 dir's to scan shouldn't affect the performance of LinuxGSM. What is the addon you are using? as there are checks for some gmod logs in LinuxGSM to clear them after x days

kerem commented

2026-02-27 02:57:51 +03:00

Author

Owner

@Donkie commented on GitHub (Aug 28, 2018):

I expected LGSM to not scan through my entire files at all every time I ran a command, why is this even necessary (especially with commands like stopping the server)? It should be up to the server software itself to check for permission issues if that's necessary in my opinion.

Even with all these directories removed it takes me atleast 5 seconds to perform the permission check.

It's a custom lua based anti cheat called Cake anti-cheat. It creates a directory for every player that joined the server with information about him. Sadly since they're not date based they can't be automatically cleaned.

@Donkie commented on GitHub (Aug 28, 2018): I expected LGSM to not scan through my entire files at all every time I ran a command, why is this even necessary (especially with commands like stopping the server)? It should be up to the server software itself to check for permission issues if that's necessary in my opinion. Even with all these directories removed it takes me atleast 5 seconds to perform the permission check. It's a custom lua based anti cheat called Cake anti-cheat. It creates a directory for every player that joined the server with information about him. Sadly since they're not date based they can't be automatically cleaned.

kerem commented

2026-02-27 02:57:51 +03:00

Author

Owner

@UltimateByte commented on GitHub (Aug 28, 2018):

This check has ben created to prevent issues while starting/stopping/updating the server. Since LinuxGSM cannot know when the user will actually make mistakes with file ownership and permission, it has to run the command every single time. While I can agree checking every time is agressive, I see no workaround, I don't want to leave the user disable the check since there would be dangerous behaviors, and ultimately, I've never seen a scenario where the delay for the check is noticeable.

@UltimateByte commented on GitHub (Aug 28, 2018): This check has ben created to prevent issues while starting/stopping/updating the server. Since LinuxGSM cannot know when the user will actually make mistakes with file ownership and permission, it has to run the command every single time. While I can agree checking every time is agressive, I see no workaround, I don't want to leave the user disable the check since there would be dangerous behaviors, and ultimately, I've never seen a scenario where the delay for the check is noticeable.

kerem commented

2026-02-27 02:57:51 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Aug 28, 2018):

It should be up to the server software itself to check for permission issues if that's necessary in my opinion.

Out of the 80+ servers, 0 do permissions checks. It's the users responsibility to check permissions normally. However, we removed that burden and added the feature for LinuxGSM to do the check instead of the user, there is no faster way to do that than using the find command. The feature has been in place for a very long time now and this is the first time an issue has been raised regarding a slowdown, so your situation is an exception to the norm.

The check is in place as many users don't understand permissions and can sometimes mess them up causing odd behaviour that's hard to diagnose. As @UltimateByte states the check is aggressive but there is no other way to guarantee that there are no permissions issues every time. Hope this explains why it has to be done.

@dgibbs64 commented on GitHub (Aug 28, 2018): ``` It should be up to the server software itself to check for permission issues if that's necessary in my opinion.``` Out of the 80+ servers, 0 do permissions checks. It's the users responsibility to check permissions normally. However, we removed that burden and added the feature for LinuxGSM to do the check instead of the user, there is no faster way to do that than using the find command. The feature has been in place for a very long time now and this is the first time an issue has been raised regarding a slowdown, so your situation is an exception to the norm. The check is in place as many users don't understand permissions and can sometimes mess them up causing odd behaviour that's hard to diagnose. As @UltimateByte states the check is aggressive but there is no other way to guarantee that there are no permissions issues every time. Hope this explains why it has to be done.

kerem commented

2026-02-27 02:57:51 +03:00

Author

Owner

@Donkie commented on GitHub (Aug 28, 2018):

I understand.

@Donkie commented on GitHub (Aug 28, 2018): I understand.

kerem commented

2026-02-27 02:57:51 +03:00

Author

Owner

@lock[bot] commented on GitHub (Aug 29, 2019):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Aug 29, 2019): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.