


How to check the current username in linux
How to check the current user name in Linux: 1. Use the id command to display the current user name, user ID, and the ID of the group to which it belongs. The syntax is "id -un"; 2. Use the whoami command. You can print the user name currently performing the operation; 3. Use the who command with the syntax "who am i" to print the user name logged in to the current Linux system.
#The operating environment of this tutorial: linux7.3 system, Dell G3 computer.
Two ways to view the current user name in Linux
Method 2: Use the id command
The Linux id command is used to display the user's ID and the ID of the group to which it belongs.
id will display the actual and effective ID of the user and the group to which they belong. If the two IDs are the same, only the actual ID is displayed. If only the user name is specified, the current user's ID will be displayed.
Print the information of the current user name. The fields of the output results are as follows:
uid: Display the user ID and user name
gid: Display the user group ID and group name
groups: Display the user's additional group ID and group name
id -------------------------------------------------------------------------------- uid=0(root) gid=0(root) groups=0(root)
Want to exploit the id Command to find the current user name, execute id -un
[root@localhost ~]# id -un root
Method 2: Use the whoami command
The whoami command in Linux is used to print the user name of the current operation. This command is equivalent to executing the "id -un
" command.
whoami
Method 3: Use the who am i
command
Linux who command is used to display the system Which users are on it? The displayed information includes user ID, terminal used, where they are connected from, online time, latency, CPU usage, actions, etc.
who am i -------------------------------------------------------------------------------- Cyuyan pts/0 2017-10-09 15:30 (:0.0)
Explanation: whoami
command vs who am i
command
whoami command and who am i command are different 2 commands, the former is used to print the user name currently performing the operation, and the latter is used to print the user name logged in to the current Linux system.
In order to better distinguish the functions of these two commands, let me give you an example. We first log in to the Linux system using the user name "Cyuyan", and then execute the following command:
[Cyuyan@localhost ~]$ whoami Cyuyan [Cyuyan@localhost ~]$ who am i Cyuyan pts/0 2017-10-09 15:30 (:0.0)
On this basis, use the su command to switch to the root user and execute the above command again:
[Cyuyan@localhost ~] su - root [root@localhost ~]$ whoami root [root@localhost ~]$ who am i Cyuyan pts/0 2017-10-09 15:30 (:0.0)
See it? Before switching the user identity, the output of the whoami and who am i commands are the same. However, after using the su command to switch the user identity, the whoami command prints the user name after the switch, while the who am i command still prints the login. The username used by the system.
Executing the whoami command is equivalent to executing the id -un command; executing the who am i command is equivalent to executing the who -m command.
In other words, using the su or sudo command to switch user identities can fool whoami, but not who am i. To explain the operating mechanism behind this, we need to understand what an actual user (UID) and an effective user (EUID, that is, Effective UID) are.
The so-called actual user refers to the user used when logging in to the Linux system. Therefore, the actual user will not change during the entire login session; and the effective user refers to the user currently performing the operation. Users, that is to say, users who really determine the level of permissions, can use the su or sudo command to switch at will.
Generally, the actual user and the effective user are the same. If there is a user identity switch, they will be different. It should be noted that there is a difference between actual users and effective users, and switching users is not the only trigger mechanism. As for other trigger conditions, subsequent chapters will introduce them in detail.
So, in what scenarios are whoami and who am i usually used? Usually, for system administrators who often need to switch users, they often need to know what identity they are currently using; in addition, for some shell scripts that require a special user to execute, you need to use the whoami command. Know who is the user who executes it; there are even some shell scripts that must be executed by a special user, even if you use the su or sudo command to switch to this identity, you need to use who am i to confirm.
Related recommendations: "Linux Video Tutorial"
The above is the detailed content of How to check the current username in linux. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)

The reasons for the installation of VS Code extensions may be: network instability, insufficient permissions, system compatibility issues, VS Code version is too old, antivirus software or firewall interference. By checking network connections, permissions, log files, updating VS Code, disabling security software, and restarting VS Code or computers, you can gradually troubleshoot and resolve issues.

VS Code is available on Mac. It has powerful extensions, Git integration, terminal and debugger, and also offers a wealth of setup options. However, for particularly large projects or highly professional development, VS Code may have performance or functional limitations.

VS Code is the full name Visual Studio Code, which is a free and open source cross-platform code editor and development environment developed by Microsoft. It supports a wide range of programming languages and provides syntax highlighting, code automatic completion, code snippets and smart prompts to improve development efficiency. Through a rich extension ecosystem, users can add extensions to specific needs and languages, such as debuggers, code formatting tools, and Git integrations. VS Code also includes an intuitive debugger that helps quickly find and resolve bugs in your code.

How to back up VS Code configurations and extensions? Manually backup the settings file: Copy the key JSON files (settings.json, keybindings.json, extensions.json) to a safe location. Take advantage of VS Code synchronization: enable synchronization with your GitHub account to automatically back up all relevant settings and extensions. Use third-party tools: Back up configurations with reliable tools and provide richer features such as version control and incremental backups.
