


How to solve the problem that the desktop service does not start when Centos starts?
Centos does not start the desktop. You can enter the character CentOS interface by modifying the system run level.
enter
# init 3
View run level
# runlevel
5 3
# # The current running level of the system is "5", the last running level was "3", and the running level conversion was successful.
Detailed description
Linux system runs on a designated run level at any time, and the programs and services of different run levels are different, and the work to be completed and the purpose to be achieved are different. Centos has set up run levels as shown in the following table, and the system can switch between these run levels to complete different tasks. Run level description
0 All processes will be terminated, the machine will stop in an orderly manner, and the system will be at this run level when shutting down
1 Single user mode. For system maintenance, only a few processes are running, and all services are not started
2 Multi-user mode. Same as run level 3, except that the Network File System (NFS) service is not started
3 Multi-user mode. Allows multiple users to log in to the system, which is the default startup level of the system
4 Leave user-defined run levels
5 Multi-user mode, and run X-Window after the system starts, giving a graphical login window
6 All processes are terminated and the system is restarted
1. If the system enters the character login CentOS interface after startup, it means that the system's default run level is 3; if the system enters the graphical login CentOS interface after startup, it means that the system's default run level is 5.
2. If the user has started the character CentOS interface and wants to enter the graphical CentOS interface, he can use the following command:
$ startx &
Run-level viewing and switching
Users can use the following command to view the runlevel runlevel of the current system. Users can use the following command to switch the runlevel init [0123456Ss]. That is, the init command is followed by a parameter. This parameter is the runlevel code of the runlevel to be switched to. ,like:
Use the init 0 command to switch to run level 0, that is, shut down (do not set initdefault to 0)
Use the init 1 command to switch to run level 1, that is, enter single-user running mode
Use the init 6 command to switch to run level 6, that is, restart (never set initdefault to 6)
You can also use the te linit command. In CentOS, the te linit command is a symbolic link to the init command.
Let’s look at an example of using runlevel and init commands:
# # Display the current running level of the system
# runlevel
N 3
# # The current running level of the system is "3", and there is no previous running level (represented by "N")
# init 2
# # After executing the "init 2" command, the corresponding stop and start service information will be displayed in the system console
# runlevel
3 2
# # The current running level of the system is "2", the last running level was "3", and the running level conversion was successful.
So change the run level of ininidefault in /etc/inittab to 2 or 3 to turn off the desktop service.
The above is the detailed content of How to solve the problem that the desktop service does not start when Centos starts?. 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











Backup and Recovery Policy of GitLab under CentOS System In order to ensure data security and recoverability, GitLab on CentOS provides a variety of backup methods. This article will introduce several common backup methods, configuration parameters and recovery processes in detail to help you establish a complete GitLab backup and recovery strategy. 1. Manual backup Use the gitlab-rakegitlab:backup:create command to execute manual backup. This command backs up key information such as GitLab repository, database, users, user groups, keys, and permissions. The default backup file is stored in the /var/opt/gitlab/backups directory. You can modify /etc/gitlab

The CentOS shutdown command is shutdown, and the syntax is shutdown [Options] Time [Information]. Options include: -h Stop the system immediately; -P Turn off the power after shutdown; -r restart; -t Waiting time. Times can be specified as immediate (now), minutes ( minutes), or a specific time (hh:mm). Added information can be displayed in system messages.

Improve HDFS performance on CentOS: A comprehensive optimization guide to optimize HDFS (Hadoop distributed file system) on CentOS requires comprehensive consideration of hardware, system configuration and network settings. This article provides a series of optimization strategies to help you improve HDFS performance. 1. Hardware upgrade and selection resource expansion: Increase the CPU, memory and storage capacity of the server as much as possible. High-performance hardware: adopts high-performance network cards and switches to improve network throughput. 2. System configuration fine-tuning kernel parameter adjustment: Modify /etc/sysctl.conf file to optimize kernel parameters such as TCP connection number, file handle number and memory management. For example, adjust TCP connection status and buffer size

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)

Steps to configure IP address in CentOS: View the current network configuration: ip addr Edit the network configuration file: sudo vi /etc/sysconfig/network-scripts/ifcfg-eth0 Change IP address: Edit IPADDR= Line changes the subnet mask and gateway (optional): Edit NETMASK= and GATEWAY= Lines Restart the network service: sudo systemctl restart network verification IP address: ip addr

Common problems and solutions for Hadoop Distributed File System (HDFS) configuration under CentOS When building a HadoopHDFS cluster on CentOS, some common misconfigurations may lead to performance degradation, data loss and even the cluster cannot start. This article summarizes these common problems and their solutions to help you avoid these pitfalls and ensure the stability and efficient operation of your HDFS cluster. Rack-aware configuration error: Problem: Rack-aware information is not configured correctly, resulting in uneven distribution of data block replicas and increasing network load. Solution: Double check the rack-aware configuration in the hdfs-site.xml file and use hdfsdfsadmin-printTopo

Building a Hadoop Distributed File System (HDFS) on a CentOS system requires multiple steps. This article provides a brief configuration guide. 1. Prepare to install JDK in the early stage: Install JavaDevelopmentKit (JDK) on all nodes, and the version must be compatible with Hadoop. The installation package can be downloaded from the Oracle official website. Environment variable configuration: Edit /etc/profile file, set Java and Hadoop environment variables, so that the system can find the installation path of JDK and Hadoop. 2. Security configuration: SSH password-free login to generate SSH key: Use the ssh-keygen command on each node

The key to installing MySQL elegantly is to add the official MySQL repository. The specific steps are as follows: Download the MySQL official GPG key to prevent phishing attacks. Add MySQL repository file: rpm -Uvh https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm Update yum repository cache: yum update installation MySQL: yum install mysql-server startup MySQL service: systemctl start mysqld set up booting
