How to execute multiple commands remotely on few servers?
I am trying to automate these steps so that I don’t need to do this on every machines manually. I need to install latest app server software (abc.tar.gz) on all the unix boxes.
sudo
Where did the “wheel” group get its name?
The wheel group on *nix computers typically refers to the group with some sort of root-like access. I’ve heard that on some *nixes it’s the group of users with the right to run su, but on Linux that seems to be anyone (although you need the root password, naturally). On Linux distributions I’ve used it seems to be the group that by default has the right to use sudo; there’s an entry in sudoers for them:
Why does cron silently fail to run sudo stuff in my script?
I have a script run from a non-privileged users’ crontab that invokes some commands using sudo. Except it doesn’t. The script runs fine but the sudo’ed commands silently fail.
How is sudo intended to be used?
I’ve tried configuring sudo before, but I haven’t had too much luck with it. How is it different from su -l -c "x"? It seems that via the configuration file, one can make it so a user can only have access to certain commands and more. I always thought of sudo as a way of one-lining a command as another user or group. Since distros like Ubuntu and Mint make it easy by essentially giving the main user easy access to root via a password, I’m not really sure what its intended use is.
How to make Fedora user a sudoer?
I want to give a Fedora user sudo privileges. How do I do that?
How could we allow non-root users to control a systemd service?
With sysvinit, a sudoers entry like this would suffice:
Why doesn’t “sudo su” in a shell script run the rest of the script as root?
A sample script can be as below:
Root access that can’t change root password?
We are having a little problem on a server. We want that some users should be able to do e.g. sudo and become root, but with the restriction that the user can’t change root password. That is, a guarantee that we still can login to that server and become root no matter of what the other users will do.
Restarting systemd service only as a specific user?
I created some systemd services which basically works:
Allowing a user to use sudo without a password
On a sandbox VM environment, I have a setup of Ubuntu Linux which is firewalled and cannot be accessed from outside the local system. Therefore, on that VM, I’d like to give the administrative user (which I set up) the ability to run anything with sudo and not need a password.