So I succesfully have locked myself out of my system, because of no root access to OSMC.
I was looking for fixing the problem “make: ldconfig: Command not found” on the internet and found that maybe adding a line to “/etc/sudoers.d/osmc-no-secure-path” would solve my problem.
After rebooting OSMC can’t boot up, just getting a sad smiley and constant trying to reload.
Is there no way to fix this?
When trying to use sudo to rewrite the file I’m getting:
/etc/sudoers.d/osmc-no-secure-path: syntax error near line 1 <<<
sudo: parse error in /etc/sudoers.d/osmc-no-secure-path near line 1
sudo: no valid sudoers sources found, quitting
sudo: unable to initialize policy plugin
Please help, I really would appreciate not having to refresh the sd-card and start on a new…
ldconfig should work fine without any issues. I’m not really sure what issues you have, but I suspect it may be due to some changes you have made on your system
Than you successfully broke something in your system
osmc@osmc:~$ sudo ldconfig --help
Usage: ldconfig.real [OPTION…]
Configure Dynamic Linker Run Time Bindings.
-c, --format=FORMAT Format to use: new, old or compat (default)
-C CACHE Use CACHE as cache file
-f CONF Use CONF as configuration file
-i, --ignore-aux-cache Ignore auxiliary cache file
-l Manually link individual libraries.
-n Only process directories specified on the command
line. Don’t build cache.
-N Don’t build cache
-p, --print-cache Print cache
-r ROOT Change to and use ROOT as root directory
-v, --verbose Generate verbose messages
-X Don’t generate links
-?, --help Give this help list
–usage Give a short usage message
-V, --version Print program version
Mandatory or optional arguments to long options are also mandatory or optional
for any corresponding short options.
But if you have issues with running ldconfig then you will have problems on your system sooner rather than later. We don’t know which commands you ran and don’t have logs to investigate.
