[GH-ISSUE #381] Add option to forcefully use root #312

New issue

Closed

opened 2026-02-27 02:00:46 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 02:00:46 +03:00

Owner

Originally created by @Scarsz on GitHub (May 13, 2015).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/381

Whenever I test out LGSM it runs in a stock, cloned virtual machine with only the root user available. In order for me to just run the script as root I have to throw a wrench into fn_check_root. I propose something like having a file in the same folder as the script "iknowwhatimdoing" that's checked inside of fn_check_root. If that file exists, skip the root check, if it doesn't exist, continue as normal.

Originally created by @Scarsz on GitHub (May 13, 2015). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/381 Whenever I test out LGSM it runs in a stock, cloned virtual machine with only the root user available. In order for me to just run the script as root I have to throw a wrench into fn_check_root. I propose something like having a file in the same folder as the script "iknowwhatimdoing" that's checked inside of fn_check_root. If that file exists, skip the root check, if it doesn't exist, continue as normal.

kerem

2026-02-27 02:00:46 +03:00

closed this issue
added the
type: feature
label

kerem commented

2026-02-27 02:00:47 +03:00

Author

Owner

@dgibbs64 commented on GitHub (May 13, 2015):

Is there any particular reason why you cannot create a non root user? I would rather not put code in to bypass as people will start using it (normally less experienced users)

@dgibbs64 commented on GitHub (May 13, 2015): Is there any particular reason why you cannot create a non root user? I would rather not put code in to bypass as people will start using it (normally less experienced users)

kerem commented

2026-02-27 02:00:47 +03:00

Author

Owner

@Scarsz commented on GitHub (May 13, 2015):

There is no particular reason that I can't, it's just a bit of an annoyance. I would recommend just not documenting it (aside from this issue, obviously) so people who have actually looked into running the script as root would see that there is a bypass available, it's just not listed anywhere, thus keeping it for more advanced users

@Scarsz commented on GitHub (May 13, 2015): There is no particular reason that I can't, it's just a bit of an annoyance. I would recommend just not documenting it (aside from this issue, obviously) so people who have actually looked into running the script as root would see that there is a bypass available, it's just not listed anywhere, thus keeping it for more advanced users

kerem commented

2026-02-27 02:00:47 +03:00

Author

Owner

@dgibbs64 commented on GitHub (May 19, 2015):

I'm afraid I will not be making any changes on this one. Using root is not a best practice and I don't want to give the option to do this even if its not published. As developers we need to practice what we preach. So stop being lazy and just create a standard user. ;-)

@dgibbs64 commented on GitHub (May 19, 2015): I'm afraid I will not be making any changes on this one. Using root is not a best practice and I don't want to give the option to do this even if its not published. As developers we need to practice what we preach. So stop being lazy and just create a standard user. ;-)

kerem commented

2026-02-27 02:00:47 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

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 (Jul 19, 2018): 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.