


Introduction to linux related commands
all all all have been dealing with Linux recently. Since I have a weak foundation in this area, I had to buy this book by Brother Niao and read it. It feels pretty good. I think the troublesome thing about Linux compared to Windows is that many things need to be controlled by commands. Of course, this is also the reason why many people like Linux. It is relatively short but powerful. In order to make it easier for everyone to find Linux-related commands, I will list the commands I know for your reference only:
System information
arch Display the processor architecture of the machine (1)
uname -m displays the machine's processor architecture (2)
uname -r displays the kernel version being used
dmidecode -q displays hardware system components - (SMBIOS / DMI)
hdparm -i /dev/hda list Architectural characteristics of a disk
hdparm -tT /dev/sda performs test read operations on the disk
cat /proc/cpuinfo displays CPU info information
cat /proc/interrupts displays interrupts
cat /proc/meminfo Verify memory usage
cat /proc/swaps Display which swaps are used
cat /proc/version Display the kernel version
cat /proc/net/dev Display network adapter and statistics
cat /proc/mounts Display the loaded file system
lspci -tv List PCI devices
lsusb -tv Display USB devices
date Display the system date
cal 2007 Display the calendar for 2007
date 041217002007.00 Set date and time - month, day, hour, minute, year, second
clock -w Save time modification to BIOS
Shutdown (system shutdown, restart and logout)
shutdown -h now Shut down the system (1)
init 0 Shut down the system (2)
telinit 0 Shut down the system (3)
shutdown -h hours:minutes & Shut down the system according to the scheduled time
shutdown -c Cancel the system shutdown according to the scheduled time
shutdown -r now Restart (1)
reboot Restart (2)
logout Logout
-
##Check whether the ssh service is installed: rpm -qa | grep ssh
-
Install ssh service: yum (-y) install ssh (redhat system such as: redhat , centos) or sudo apt -get install ssh (debian system such as: ubunt)
View the process the program is running: ps -ef | grep weblogic
Kill Process: kill -9 process number
Start ssh (generally called sshd) process: service sshd start or Use /etc/init.d/sshd start
- installation command: yum/rpm/apt
Check the output file: tail -f nohup.out Background startup: nohup ./startWeblogic.sh |
Super copy: |
scp fromfilePath tofilePath(userName@IP:/filePath) forExample: scp isportal_uum_sj.tar.gz.0928 root@172.16.66.18:/opt /apache-tomcat-6.0.37/webapps |
ntpdate cn.pool.ntp.org sysctl -w net.ipv4.tcp_tw_recycle=1
yum -y install gcc make gcc-c++ openssl-devel
The above is the detailed content of Introduction to linux related commands. 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

AI Hentai Generator
Generate AI Hentai for free.

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



Steps to start Nginx in Linux: Check whether Nginx is installed. Use systemctl start nginx to start the Nginx service. Use systemctl enable nginx to enable automatic startup of Nginx at system startup. Use systemctl status nginx to verify that the startup is successful. Visit http://localhost in a web browser to view the default welcome page.

How to confirm whether Nginx is started: 1. Use the command line: systemctl status nginx (Linux/Unix), netstat -ano | findstr 80 (Windows); 2. Check whether port 80 is open; 3. Check the Nginx startup message in the system log; 4. Use third-party tools, such as Nagios, Zabbix, and Icinga.

Starting an Nginx server requires different steps according to different operating systems: Linux/Unix system: Install the Nginx package (for example, using apt-get or yum). Use systemctl to start an Nginx service (for example, sudo systemctl start nginx). Windows system: Download and install Windows binary files. Start Nginx using the nginx.exe executable (for example, nginx.exe -c conf\nginx.conf). No matter which operating system you use, you can access the server IP

The server does not have permission to access the requested resource, resulting in a nginx 403 error. Solutions include: Check file permissions. Check the .htaccess configuration. Check nginx configuration. Configure SELinux permissions. Check the firewall rules. Troubleshoot other causes such as browser problems, server failures, or other possible errors.

How to fix Nginx 403 Forbidden error? Check file or directory permissions; 2. Check .htaccess file; 3. Check Nginx configuration file; 4. Restart Nginx. Other possible causes include firewall rules, SELinux settings, or application issues.

Answer to the question: 304 Not Modified error indicates that the browser has cached the latest resource version of the client request. Solution: 1. Clear the browser cache; 2. Disable the browser cache; 3. Configure Nginx to allow client cache; 4. Check file permissions; 5. Check file hash; 6. Disable CDN or reverse proxy cache; 7. Restart Nginx.

In Linux, use the following command to check whether Nginx is started: systemctl status nginx judges based on the command output: If "Active: active (running)" is displayed, Nginx is started. If "Active: inactive (dead)" is displayed, Nginx is stopped.

The error log is located in /var/log/nginx (Linux) or /usr/local/var/log/nginx (macOS). Use the command line to clean up the steps: 1. Back up the original log; 2. Create an empty file as a new log; 3. Restart the Nginx service. Automatic cleaning can also be used with third-party tools such as logrotate or configured.
