


Linux provides several different types of users
Linux stipulates three different types of users, namely: 1. Super user. The super user’s user name is root, which has all operating rights; 2. System user. The system user is responsible for the normal operation of the Linux system. The necessary built-in users are generally used for management services; 3. Ordinary users. Ordinary users are created to allow users to use Linux system resources. The accounts created by users are generally ordinary accounts.
#The operating environment of this tutorial: linux5.9.8 system, Dell G3 computer.
Linux provides several different types of users?
##3.
Brief description of Linux user types
Linux system is a multi-user and multi-tasking operating system. Each user Everyone has an independent identity number, which is the user ID (UID). In Linux, the user does not know the user's user name, but it actually knows the user ID—UID.Users under Linux are divided into three categories: super user (root), system user, and ordinary user.
The user name of the super user is root, which has all operating rights. Therefore, for the sake of security, it is recommended not to easily operate files under the root account. In the character interface of the Linux operating system, the prompt for the root account is #, and by default, the UID of the root user is 0. The system user is a built-in user necessary for the normal operation of the Linux system. It is generally used for management services. System users cannot be used to log in, such as bin, daemon, lp and other users. The UID of system users is generally 1~499, and their shell is /sbin/nologin. Ordinary users are created to allow users to use Linux system resources. The accounts created by users are generally ordinary accounts. In the character interface of the Linux operating system, the prompt for ordinary users is $, and the default UID for ordinary users is 1000~60000. Linux system also inherits the practice of Unix system, using plain text files to save various account information. Users can manage users and groups by modifying text files.The user-related files are:
/etc/passwd (user account file, accessible to all accounts) 7 sections in total, The format is as follows:
Username: Password: UID: GID: Account information: Account directory: Shell version
/etc/shadow ( User password file (can only be accessed by root), with a total of 9 paragraphs, the format is as follows:
Username: Password: Number of days since the last modification: Minimum number of days between two password modifications: How many days will it take to change the password again? Change password: The number of days from when the warning is issued to the official expiration of the password: The number of days the username is still valid before the login is prohibited: The time the user is prohibited from logging in: Flag field, unintentionalmeaning
Note: shadow In the password field, * indicates that the user is prohibited from logging in, "!!" indicates that the user has not set a password, and "!" indicates that the user is locked.
The password of passwd is the shadow password represented by X, and the shadow is the encrypted and saved ciphertext.
The file related to the user group is:
/etc/group (user group file, accessible to all accounts) , a total of 4 paragraphs, the format is as follows:
User group name: Group password: GID: Group member
/etc/gshadow (User group Password file, which can only be accessed with root permission) There are 4 paragraphs in total, the format is as follows:
User group name: Group password: Group manager: Group member
Related recommendations: "Linux Video Tutorial"
The above is the detailed content of Linux provides several different types of users. 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).

The key differences between CentOS and Ubuntu are: origin (CentOS originates from Red Hat, for enterprises; Ubuntu originates from Debian, for individuals), package management (CentOS uses yum, focusing on stability; Ubuntu uses apt, for high update frequency), support cycle (CentOS provides 10 years of support, Ubuntu provides 5 years of LTS support), community support (CentOS focuses on stability, Ubuntu provides a wide range of tutorials and documents), uses (CentOS is biased towards servers, Ubuntu is suitable for servers and desktops), other differences include installation simplicity (CentOS is thin)

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.

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).

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)

Docker uses Linux kernel features to provide an efficient and isolated application running environment. Its working principle is as follows: 1. The mirror is used as a read-only template, which contains everything you need to run the application; 2. The Union File System (UnionFS) stacks multiple file systems, only storing the differences, saving space and speeding up; 3. The daemon manages the mirrors and containers, and the client uses them for interaction; 4. Namespaces and cgroups implement container isolation and resource limitations; 5. Multiple network modes support container interconnection. Only by understanding these core concepts can you better utilize Docker.

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.

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.
