View Linux log

Linux log view 1. view all the hardware information of the machine: dmidecode | more dmesg | more commands contain a large amount of information. Therefore, we recommend that you use "| more" to view more information. method 1: CPU-related parameters in Linux are saved in the/proc/cpuinfo file cat/proc/cpuinfo | more Method 2: run the command dmesg | grep CPU to view the CPU startup information and check the CPU bits: getconf LONG_BIT 3. view Mem information cat/proc/meminfo | more (note the last line of output information: MachineMem: 41932272 kB) free-m top 4. method 1: fdisk-l shows the partition and size of the disk (including the USB flash disk) on the system. Method 2: View cat/proc/partitions 5. method 1: ethtool eth0 can use this command to view NIC-related technical indicators (not all network cards support this command) ethtool-I eth1 add-I parameter view NIC driver you can try other parameters to view Nic related technical parameters method 2: You can also see the NIC name through dmesg | grep eth0 (manufacturer) and other information by viewing/etc/sysconfig/network-scripts/ifcfg-eth0 can see the current Nic configuration including IP, gateway address and other information. You can also run the ifconfig command. 6. How to view the motherboard information? Lspci 7. how to mount the ISO file mount-o loop *. iso mount_point8. method 1: After the CD is inserted, in my RHEL5 system, the CD file is/dev/cdrom. Therefore, you only need to mount/dev/cdrom mount_point. [Root @ miix tmp] # mount/dev/cdrom mount_point mount: block device/dev/cdrom is write-protected, mounting read-only actually takes a closer look, the device file of the optical drive is hdc [root @ miix tmp] # ls-l/dev/cdrom * lrwxrwxrwx 1 root 3 01-08 08:54/dev/cdrom-> hdc lrwxrwxrwx 1 root root 3 01-08/dev/cdrom-hdc-> hdc, so we can also mount/dev/hdc mount_point in this way if the drive does not contain a valid disc, the following error occurs: [root @ miix tmp] # mount/dev/hdc mount_point mount: media not found 9. how to query Method 1: You can use the fdisk-l command to view the information of the USB flash drive. The information of your USB flash drive is as follows: Disk/dev/sda: 2012 MB, 2012217344 bytes 16 heads, 32 sectors/track, 7676 cylinders Units = cylinders of 512*512 = 262144 bytes Device Boot Start End Blocks Id System/dev/sda1 * 16 7676 1961024 B W95 FAT32 USB flash drive Device file is/dev/sda, 2 GB size, in FAT32 format. If the user logs on to the Linux GUI, the USB flash drive will not be automatically mounted. In this case, run the mount: mount/dev/sda1 mount_point command or above to mount the USB flash disk to the mount_point directory in the current directory. Note that sda1 is not sda. The unmount command is umount mount_point by default. Linux does not have a built-in drive that supports NTFS-format disks, but FAT32 is well supported. The-t vfat parameter is generally not required for mounting. If ntfs is supported, the-t ntfs parameter should be used for ntfs-format disk partitions. In case of garbled characters, you can consider using the-o iocharset = Character Set parameter. In fact, it can be said that it is a monitoring system record, and the system will basically record every action. In this way, the information is very comprehensive and important. Generally, only the root user can perform inspections! You can use the logon file (Log File) to solve most of the Linux problems based on the error messages on the screen and the error messages matching the logon file! Therefore, log files are very important. As a qualified linux system engineer, log files must be mastered. Common Logon files include/var/log/secure: files that log on to the system to access data, such as pop3, ssh, telnet, and ftp; /var/log/wtmp: records the information data of the login user. Because this file has been encoded, you must use the last command to retrieve the file content;/var/log/messages: it is particularly important that almost any error message (or important information) is recorded here;/var/log/boot. log: records the startup or shutdown messages displayed when a service is started./var/log/maillog or/var/log/mail /*: record the user record of email access or exchange (sendmail and pop3);/var/log/cron: record the contents of the crontab routine service. /Var/log/httpd,/var/log/news,/var/log/mysqld. log,/var/log/samba,/var/log/procmail. log: several different network service record files! One of the record programs in the logon file: syslogd usually records data after syslog: the date and time of the event; Host Name of the event; the service name (such as samba and xinetd) or function name (such as libpam ..) that starts this event ..); the daemon configuration file of syslogd is/etc/syslog. the conf content syntax is as follows: Service name [. =!] File name or device or host of the information level message record