On my system the variable $SUDO_USER is set to the caller’s user name. You shouldn’t extract the username from the ${HOME} variable directly. It’s being configured and not calculated. To Extract the username you could take a look into /etc/passwd file, but this is very system dependent, e.g. sometimes you have to look into a … Read more
Edit the sudoers file (with visudo) and add a rule that allows the web server user to run the command without a password. For example: www-data ALL=NOPASSWD: /path/to/script
If you are using Chocolatey (a package manager), you can install a package named sudo. Then you can use sudo like Linux 😋
To get the password, just put sudo echo “Thanks.” at the start of the script. But I would prefer this solution: if [[ $UID != 0 ]]; then echo “Please run this script with sudo:” echo “sudo $0 $*” exit 1 fi
The solution is to use the -b flag for sudo to run the command in the background: $ sudo -b ./ascii_loader_script.pl 20070502 ctm_20070502.csv You should only use nohup if you want the program to continue even after you close your current terminal session
Run bash as sudo: $ sudo bash -c “cat add_file >> /etc/file” $ whoami;sudo bash -c “whoami”;whoami iiSeymour root iiSeymour
For those trying to run custom command using the official docker image, use the following command. docker-entrypoint.sh handles switching the user and handling other permissions. docker-entrypoint.sh -c ‘shared_buffers=256MB’ -c ‘max_connections=200’
How can I install to a path under my home directory? mkdir /home/masi/.local cd Python-2.6.1 make clean ./configure –prefix=/home/masi/.local make make install Then run using: /home/masi/.local/bin/python Similarly if you have scripts (eg. CGI) that require your own user version of Python you have to tell them explicitly: #!/home/masi/.local/bin/python instead of using the default system Python … Read more
This seems to be a bug introduced in 10.8, see this report. As far as I can tell, the only workaround is not setting DYLD_LIBRARY_PATH or LD_LIBRARY_PATH by default, but only when needed.
You can own the file you want to edit, then give it back the ownership afterwards sudo chown myuser /path/to/file code /path/to/file sudo chown root /path/to/file