debian su – and su $PATH differences?
The two implementations are very similar but have some minor differences (and there might be more that was not yet noticed ofcourse), e.g.
The two implementations are very similar but have some minor differences (and there might be more that was not yet noticed ofcourse), e.g.
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:
A sample script can be as below:
I know what should be the difference between su and su -, but in my system (Debian) for example PATH is the same:
This question has been asked in a different way in other forums. But there has not been a decent explanation why you can’t do the below in bash.
Every time I log into a VM with root, su into a user account, and try to use screen it throws an error:
Let’s say I have 2 user accounts user1 and user2. When I login as user1, and then switch to user2 using su, I can execute command-line programs, but GUI programs fail.
I have a remote host,
previously I can ssh into it with root and password
On my personal machine, I often type sudo in front of certain commands in order to accomplish administrative tasks. I had hoped to avoid doing this throughout the day, by typing su root and providing the same password I usually do for sudo. However, the two passwords are not the same(I don’t know how to log in to su root). Is running a command with sudo different than logging in with su root and running the same command?
I am able to run anything using sudo; my password is accepted. But whenever I try to do su from a shell, it fails with: