What I want is to find the name of the user that runs bash script, when this script is executed by sudo. The only possible way, that I know, is to parse the output of who -m (who am i) in this way:

user@UbuntuServer:~$ cat who.sh 
echo $USER
who -m | awk '{print $1}'

user@UbuntuServer:~$ sudo ./who.sh 

The problem is: In Ubuntu Desktop 16.04.4 who -m (resp. who am i) do nothing. Why?

enter image description here

Another question is why the Ubuntu's online manual page for who is different from man who executed either on Ubuntu Desktop or Server?

But these questions are not so important according to my goals. And as it is mentioned in the title, the main question is: How do I find which user executes the script when is used sudo?

Practically, the original title - How do I find 'who am I' on Ubuntu Desktop? - is the same but wrongly asked question.

  • 3
    "who am I" is not a command. The command is whoami . Note no spaces and no cap I (whoamI is NOT the same as whoami). The command who is working as expected, what output were you expecting ?
    – Panther
    May 9, 2018 at 6:22
  • 3
    @Panther, who am i is synopsis of who, please check the section OPERANDS in man who. I know whoami is different command. I'm expecting some any output of who -m or who am i, but there is no output. I updated the question.
    – pa4080
    May 9, 2018 at 6:30
  • 2
    See unix.stackexchange.com/questions/55874/… .
    – Panther
    May 9, 2018 at 6:41
  • 1
    There is a descussion about why the change in Fedora - bugzilla.redhat.com/show_bug.cgi?id=1280724 . I can not find a Debian specific discussion but I suspect it has something to do with "You ask why this was removed. The issue was that this was the implementation requires setuid or setgid helpers to elevate privileges to write to the single shared file. In addition, the mechanism is broken because there's no cleanup when a session crashes, so the data this returns cannot be trusted for anything anyway. The same information can be retrieved from other sources in a more reasonable way."
    – Panther
    May 9, 2018 at 6:57
  • 1

2 Answers 2


I had a similar problem a while ago, and the only way that has worked reliably for me so far, is:

echo ${SUDO_USER:-${USER}}

As long as the user works with the shell as himself, $USER contains his username. When he calls sudo, for the new subshell $SUDO_USER is set to what is $USER in the calling shell, and $USER becomes root, of course.

The trick with the operator :- is, that the whole expression evaluates to $SUDO_USER if it is set (so inside the subshell opened by sudo), and otherwise to $USER. Therefore, you always have the correct username and don't have to worry much about the context the expression is evaluated in, which I found to be convenient.

  • 1
    Interesting. I'll have try this +1. May 9, 2018 at 17:50

While the solution provided by Wanderer works as it is expected, and it is straight answer to the question, for the past few years when I want to force the script to be executed by certain (system) user I am using the special environment variable Eeffective UID - $EUID.

[[ $EUID -ne $SCRIPT_UID ]] && {
  echo "Please run as $(id $SCRIPT_UID -un), use: sudo -u $(id $SCRIPT_UID -un) $0"
  exit 1
echo "The script is running as $(id $EUID -un)."
  • 1
    This does not work. The OP wanted to know the UID of user who started sudo. This is in $SUDO_USER or $SUDO_UID. On the other hand, $EUID (as the name implies - effective UID) gives the UID of user sudo has switched to (exactly as used in your example). So it's the opposite of what OP asked.
    – raj
    Jul 25, 2022 at 11:38
  • 1
    Hello, @raj, I'm totally agree with you! However, because I'm the original poster, I remember the main purpose of this question was to make such test, so I decided this is a good place to share also this solution.
    – pa4080
    Jul 25, 2022 at 12:10

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .