Linux的shell程式設計前奏常見命令實戰三
阿新 • • 發佈：2018-12-22
Linux的shell程式設計前奏常見命令實戰三
一>linux下通過mkdir建立一個新目錄/oldboy/ett,ett的硬連結數是多少，為什麼？
如果在/oldboy/ett下面再建立一個目錄test,那麼，ett的硬連結數是多少，為什麼？
[
[email protected] oldboy]# mkdir -p /oldboy/ett -------建立/oldboy/ett [[email protected] oldboy]# ls -l /oldboy-------檢視硬連結數為2(本身為一個,.為一個) 總用量 4 drwxr-xr-x 2 root root 6 12月 10 20:44 ett -rw-r--r-- 1 rsync rsync 0 7月 29 14:45 haohao2 -rw-r--r-- 1 rsync rsync 0 7月 29 14:45 haohao3 -rw-r--r-- 1 rsync rsync 0 7月 29 14:45 haohao4 -rw-r--r-- 1 rsync rsync 0 7月 29 14:45 haohao5 -rw-r--r-- 1 rsync rsync 0 7月 29 14:45 haohao6 -rw-r--r-- 1 rsync rsync 0 7月 29 14:45 haohao7 -rw-r--r-- 1 rsync rsync 0 7月 29 14:45 haohao8 -rw-r--r-- 1 rsync rsync 0 7月 29 14:45 haohao9 -rw-r--r-- 1 root root 11 7月 29 10:12 test -rw-r--r-- 1 rsync rsync 0 7月 29 10:26 test1 -rw-r--r-- 1 rsync rsync 0 7月 29 10:26 test10 -rw-r--r-- 1 rsync rsync 0 7月 29 10:26 test2 -rw-r--r-- 1 rsync rsync 0 7月 29 10:26 test3 -rw-r--r-- 1 rsync rsync 0 7月 29 10:26 test4 -rw-r--r-- 1 rsync rsync 0 7月 29 10:26 test5 -rw-r--r-- 1 rsync rsync 0 7月 29 10:26 test6 -rw-r--r-- 1 rsync rsync 0 7月 29 10:26 test7 -rw-r--r-- 1 rsync rsync 0 7月 29 10:26 test8 -rw-r--r-- 1 rsync rsync 0 7月 29 10:26 test9 -rw-r--r-- 1 root root 0 7月 29 10:24 testa -rw-r--r-- 1 root root 0 7月 29 10:24 testb -rw-r--r-- 1 root root 0 7月 29 10:24 testc -rw-r--r-- 1 root root 0 7月 29 10:24 testd -rw-r--r-- 1 root root 0 7月 29 10:24 teste -rw-r--r-- 1 root root 0 7月 29 10:24 testf -rw-r--r-- 1 root root 0 7月 29 10:24 testg [[email protected] ett]# ls -l /oldboy/ett -di -----第一個硬連結 34175539 drwxr-xr-x 2 root root 6 12月 10 20:44 /oldboy/ett [[email protected] ett]# ls -l /oldboy/ett -ai ------第二個硬連結 總用量 4 34175539 drwxr-xr-x 2 root root 6 12月 10 20:44 . 34351858 drwxrwxrwx 3 rsync rsync 4096 12月 10 20:44 .. ------------------------------------------------------------------------------------------------------------------------------------ [[email protected] ett]# mkdir test [[email protected] ett]# cd ..;ll|grep ett drwxr-xr-x 3 root root 18 12月 10 21:17 ett [[email protected] oldboy]# ll /oldboy/ett -di 34175539 drwxr-xr-x 3 root root 18 12月 10 21:17 /oldboy/ett ----第一個硬連結 [[email protected] oldboy]# ll /oldboy/ett -ai 總用量 4 34175539 drwxr-xr-x 3 root root 18 12月 10 21:17 . ----第二個硬連結 34351858 drwxrwxrwx 3 rsync rsync 4096 12月 10 20:44 .. 34175540 drwxr-xr-x 2 root root 6 12月 10 21:17 test [[email protected] oldboy]# cd /oldboy/ett/test;ll 總用量 0 [[email protected] test]# cd /oldboy/ett/test;ls -lai|grep "\.\." 34175539 drwxr-xr-x 3 root root 18 12月 10 21:17 .. ----第三個硬連結
總結:
1>硬連結
A.具有相同inode節點號的多個檔案互為硬連結檔案。
B.刪除硬連結檔案或者刪除原始檔任意之一，檔案實體並未刪除；只有刪除了原始檔以及原始檔所有
對應的硬連結檔案，檔案實體才會被刪除。
C.硬連結檔案就是檔案的另外一個入口（相當於超市的前後門）。
2>軟連結
A.軟連結類似於windows檔案的快捷方式。
B.軟連結類似於一個文字檔案，裡面存放的是原始檔的路勁，指向原始檔實體；即使刪除了原始檔，
軟連結檔案也還是依然存在，但是無法訪問指向的原始檔路徑內容了。
C.軟連結和原始檔是不同型別的檔案，也是不同的檔案，inode號也不相同。
二>請給出預設情況下ens33網絡卡配置檔案的路徑及客戶端dns的路徑.
[[email protected] etc]# cat /etc/sysconfig/network-scripts/ifcfg-ens33 -----預設情況下ens33網絡卡配置檔案的路徑 TYPE=Ethernet HWADDR=00:0c:29:47:b5:b6 BOOTPROTO=dhcp DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_PEERDNS=yes IPV6_PEERROUTES=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=ens33 UUID=b794f3ad-8259-4075-9cde-faf5a14b434b DEVICE=ens33 ONBOOT=yes ZONE= [[email protected] etc]# cat /etc/resolv.conf ------客戶端dns的路徑. ; generated by /usr/sbin/dhclient-script search DHCP HOST nameserver 192.168.1.1 nameserver 192.168.0.1
三>執行下面命令時發現提示需要輸入密碼，請問提示輸入的密碼是哪個使用者的密碼?
[[email protected]] sudo su - oldboy
當前執行命令test使用者的密碼。
總結:
1>su -/ su - root 該命令是真正使用者角色轉換命令（預設是切到root）,輸入的是root密碼。
2>sudo su - 該命令是通過sudo許可權進行角色轉換(預設是切到root),輸入的是執行命令當時執行命令對應使用者的密碼，非root密碼。
3>sudo su - oldboy 該命令實際意思是通過sudo,以root的許可權，進行su - oldboy使用者切換，因此需要輸入的是執行命令當時使用者的密碼。
四>已知/oldboy/test.txt檔案內容為
test
liyao
oldboy
請問如何把檔案中的空行過濾掉（要求命令列實現）
[[email protected] /]# cat test.txt test liyao oldboy 法一: [[email protected] /]# grep -v "^$" test.txt test liyao oldboy 法二: [[email protected] /]# sed '/^$/d' test.txt test liyao oldboy
五>請描述下列路徑是做什麼的？
/var/log/messages
/var/log/secure
/var/spool/clientmqueue
/proc/interrupts
/etc/fstab
/etc/profile
答案: /var/log/messages 系統日誌
/var/log/secure 系統安全日誌
/var/spool/clientmqueue 郵件臨時目錄
/proc/interrupts 檢視中斷檔案
/etc/fstab 磁碟檔案系統開機自動掛載檔案
/etc/profile 全域性的環境配置檔案
六>如何快速查到ifconfig的全路徑?
法一:
[[email protected] /]# which ifconfig -------- which檢視系統命令的路徑
/usr/sbin/ifconfig
法二:
[[email protected] /]# whereis -b ifconfig ------- -b是檢視二進位制命令
ifconfig: /usr/sbin/ifconfig
七>檢視當前哪些使用者線上的linux命令?
[[email protected] /]# w --------w 20:52:00 up 48 min, 2 users, load average: 0.02, 0.04, 0.05 USER TTY FROM [email protected] IDLE JCPU PCPU WHAT root tty1 20:08 43:52 0.31s 0.31s -bash root pts/0 192.168.0.101 20:08 0.00s 0.56s 0.03s w [[email protected] /]# last -------last root pts/0 192.168.0.101 Sat Dec 22 20:08 still logged in root tty1 Sat Dec 22 20:08 still logged in reboot system boot 3.10.0-514.el7.x Sat Dec 22 20:03 - 20:52 (00:48) root pts/0 192.168.0.101 Thu Dec 20 22:30 - down (00:15) root tty1 Thu Dec 20 22:25 - 22:46 (00:21) reboot system boot 3.10.0-514.el7.x Thu Dec 20 22:18 - 22:46 (00:28) root pts/0 192.168.0.103 Sun Dec 16 22:13 - crash (4+00:04) root tty1 Sun Dec 16 22:13 - crash (4+00:05) reboot system boot 3.10.0-514.el7.x Sun Dec 16 22:11 - 22:46 (4+00:34) root pts/0 192.168.0.101 Thu Dec 13 21:00 - down (01:39) root tty1 Thu Dec 13 20:50 - 22:39 (01:49) reboot system boot 3.10.0-514.el7.x Thu Dec 13 20:49 - 22:39 (01:50) root pts/0 192.168.0.101 Mon Dec 10 20:19 - down (02:13) root tty1 Mon Dec 10 20:18 - 22:32 (02:14) reboot system boot 3.10.0-514.el7.x Mon Dec 10 20:15 - 22:33 (02:17) root pts/0 192.168.0.102 Sun Dec 9 22:18 - down (00:12) root tty1 Sun Dec 9 22:18 - 22:30 (00:12) reboot system boot 3.10.0-514.el7.x Sun Dec 9 22:12 - 22:30 (00:18) root pts/0 192.168.0.101 Sun Oct 28 12:47 - down (06:38) root tty1 Sun Oct 28 12:46 - 19:24 (06:38) reboot system boot 3.10.0-514.el7.x Sun Oct 28 12:45 - 19:25 (06:39) root pts/0 192.168.0.101 Sat Oct 13 17:51 - down (04:34) root tty1 Sat Oct 13 17:51 - 22:26 (04:35) reboot system boot 3.10.0-514.el7.x Sat Oct 13 17:49 - 22:26 (04:36) reboot system boot 3.10.0-514.el7.x Sat Oct 13 17:32 - 22:26 (04:54) reboot system boot 3.10.0-514.el7.x Sat Oct 13 17:00 - 22:26 (05:26) root pts/0 192.168.0.101 Mon Oct 1 17:16 - down (05:32) root tty1 Mon Oct 1 17:15 - 22:48 (05:32) reboot system boot 3.10.0-514.el7.x Mon Oct 1 17:02 - 22:48 (05:46) root pts/0 192.168.0.101 Mon Oct 1 14:02 - down (02:32) root tty1 Mon Oct 1 14:02 - 16:35 (02:32) reboot system boot 3.10.0-514.el7.x Mon Oct 1 10:38 - 16:35 (05:56) root pts/0 192.168.0.101 Mon Sep 24 08:03 - down (13:33) root tty1 Mon Sep 24 08:03 - 21:36 (13:33) reboot system boot 3.10.0-514.el7.x Mon Sep 24 08:01 - 21:37 (13:35) root pts/0 192.168.0.101 Sun Sep 23 19:39 - 23:02 (03:22) root tty1 Sun Sep 23 19:39 - 23:02 (03:22) reboot system boot 3.10.0-514.el7.x Sun Sep 23 19:37 - 23:02 (03:25) root pts/0 192.168.0.102 Sat Sep 22 21:06 - down (00:41) root tty1 Sat Sep 22 21:06 - 21:48 (00:42) reboot system boot 3.10.0-514.el7.x Sat Sep 22 21:01 - 21:48 (00:47) root pts/0 192.168.0.102 Mon Sep 17 11:26 - down (11:03) root tty1 Mon Sep 17 11:23 - 22:29 (11:06) reboot system boot 3.10.0-514.el7.x Mon Sep 17 10:50 - 22:30 (11:39) root pts/0 192.168.0.103 Sun Sep 16 10:56 - down (11:19) root tty1 Sun Sep 16 10:56 - 22:16 (11:20) reboot system boot 3.10.0-514.el7.x Sun Sep 16 10:51 - 22:16 (11:24) root pts/0 192.168.0.102 Sat Sep 15 16:26 - down (05:49) root tty1 Sat Sep 15 16:18 - 22:15 (05:57) reboot system boot 3.10.0-514.el7.x Sat Sep 15 16:17 - 22:16 (05:59) root pts/0 192.168.0.102 Wed Sep 12 21:49 - down (01:05) root tty1 Wed Sep 12 20:28 - 22:54 (02:26) reboot system boot 3.10.0-514.el7.x Wed Sep 12 20:21 - 22:54 (02:33) root pts/0 192.168.0.104 Tue Sep 11 19:10 - down (03:17) root tty1 Tue Sep 11 19:09 - 22:28 (03:18) reboot system boot 3.10.0-514.el7.x Tue Sep 11 19:08 - 22:28 (03:19) root pts/0 192.168.0.104 Mon Sep 10 22:28 - down (00:26) root tty1 Mon Sep 10 22:27 - 22:54 (00:26) reboot system boot 3.10.0-514.el7.x Mon Sep 10 16:18 - 22:54 (06:35) root pts/0 192.168.0.101 Sun Sep 9 11:04 - crash (1+05:14) root tty1 Sun Sep 9 11:03 - crash (1+05:14) reboot system boot 3.10.0-514.el7.x Sun Sep 9 08:30 - 22:54 (1+14:23) root pts/0 192.168.0.101 Sat Sep 8 14:05 - down (08:58) root tty1 Sat Sep 8 14:04 - 23:03 (08:59) reboot system boot 3.10.0-514.el7.x Sat Sep 8 14:01 - 23:03 (09:02) root pts/0 192.168.0.101 Fri Sep 7 20:30 - crash (17:30) root tty1 Fri Sep 7 20:30 - crash (17:31) reboot system boot 3.10.0-514.el7.x Fri Sep 7 19:55 - 23:03 (1+03:07) root tty1 Thu Sep 6 22:54 - 22:54 (00:00) reboot system boot 3.10.0-514.el7.x Thu Sep 6 21:43 - 22:54 (01:11) root pts/0 192.168.0.102 Tue Sep 4 22:07 - down (01:27) root tty1 Tue Sep 4 22:04 - 23:35 (01:30) reboot system boot 3.10.0-514.el7.x Tue Sep 4 22:02 - 23:35 (01:32) root pts/1 192.168.0.102 Sun Sep 2 12:12 - 17:14 (05:01) root pts/1 192.168.0.102 Sun Sep 2 11:48 - 12:05 (00:16) root pts/0 192.168.0.102 Sun Sep 2 10:05 - crash (2+11:57) root tty1 Sun Sep 2 10:05 - crash (2+11:57) reboot system boot 3.10.0-514.el7.x Sun Sep 2 10:04 - 23:35 (2+13:31) root pts/0 192.168.0.102 Sat Sep 1 23:37 - down (00:04) root tty1 Sat Sep 1 23:36 - 23:41 (00:04) reboot system boot 3.10.0-514.el7.x Sat Sep 1 23:34 - 23:41 (00:06) root pts/0 192.168.0.102 Sat Sep 1 22:39 - crash (00:55) root tty1 Sat Sep 1 22:33 - crash (01:01) reboot system boot 3.10.0-514.el7.x Sat Sep 1 22:19 - 23:41 (01:21) root pts/0 192.168.0.102 Thu Aug 30 22:54 - 23:20 (00:25) root tty1 Thu Aug 30 22:53 - crash (1+23:26) reboot system boot 3.10.0-514.el7.x Thu Aug 30 22:45 - 23:41 (2+00:56) root pts/0 192.168.0.102 Wed Aug 29 21:18 - down (02:09) root tty1 Wed Aug 29 21:17 - 23:27 (02:10) reboot system boot 3.10.0-514.el7.x Wed Aug 29 21:13 - 23:27 (02:14) root pts/0 192.168.0.102 Mon Aug 27 19:53 - crash (2+01:19) root tty1 Mon Aug 27 19:53 - crash (2+01:20) reboot system boot 3.10.0-514.el7.x Mon Aug 27 19:46 - 23:27 (2+03:41) root pts/1 192.168.0.102 Sun Aug 26 22:26 - 22:47 (00:21) root pts/0 192.168.0.102 Sun Aug 26 20:34 - 23:37 (03:03) root tty1 Sun Aug 26 20:33 - crash (23:12) reboot system boot 3.10.0-514.el7.x Sun Aug 26 20:32 - 23:27 (3+02:55) root pts/0 192.168.0.102 Fri Aug 24 22:55 - down (00:11) root pts/0 192.168.0.102 Fri Aug 24 21:54 - 22:54 (01:00) root tty1 Fri Aug 24 21:53 - 23:06 (01:12) reboot system boot 3.10.0-514.el7.x Fri Aug 24 21:41 - 23:06 (01:24) root pts/0 192.168.0.103 Sun Aug 19 10:34 - crash (5+11:07) root tty1 Sun Aug 19 10:31 - crash (5+11:10) reboot system boot 3.10.0-514.el7.x Sun Aug 19 09:37 - 23:06 (5+13:28) root pts/0 192.168.0.103 Sat Aug 18 20:28 - down (02:02) root tty1 Sat Aug 18 20:24 - 22:30 (02:05) reboot system boot 3.10.0-514.el7.x Sat Aug 18 20:21 - 22:30 (02:09) root tty1 Sat Aug 18 18:59 - 20:13 (01:14) reboot system boot 3.10.0-514.el7.x Sat Aug 18 18:51 - 20:14 (01:22) root tty1 Sat Aug 18 18:55 - 18:57 (00:02) reboot system boot 3.10.0-514.el7.x Sat Aug 18 18:42 - 20:14 (01:31) root tty1 Sun Aug 5 10:02 - crash (13+08:40) reboot system boot 3.10.0-514.el7.x Sun Aug 5 09:55 - 20:14 (13+10:18) root pts/1 192.168.0.102 Sun Jul 29 21:37 - 21:37 (00:00) root pts/1 192.168.0.102 Sun Jul 29 21:20 - 21:20 (00:00) root pts/0 192.168.0.102 Sun Jul 29 16:33 - down (06:49) root tty1 Sun Jul 29 16:31 - 23:22 (06:50) reboot system boot 3.10.0-514.el7.x Sun Jul 29 16:30 - 23:22 (06:51) root pts/0 192.168.0.102 Sun Jul 29 10:37 - crash (05:52) root tty1 Sun Jul 29 10:35 - crash (05:55) reboot system boot 3.10.0-514.el7.x Sun Jul 29 10:31 - 23:22 (12:51) root pts/0 192.168.0.102 Sun Jul 29 08:13 - crash (02:17) root tty1 Sun Jul 29 08:01 - crash (02:29) reboot system boot 3.10.0-514.el7.x Sun Jul 29 07:41 - 23:22 (15:40) root pts/0 192.168.0.102 Sat Jul 28 22:21 - down (00:37) root tty1 Sat Jul 28 22:20 - 22:58 (00:37) reboot system boot 3.10.0-514.el7.x Sat Jul 28 22:18 - 22:58 (00:40) root pts/0 192.168.0.102 Sat Jul 28 19:42 - down (01:52) root tty1 Sat Jul 28 19:41 - 21:35 (01:53) reboot system boot 3.10.0-514.el7.x Sat Jul 28 19:40 - 21:35 (01:54) root pts/1 192.168.0.102 Sat Jul 28 10:30 - crash (09:10) root pts/0 192.168.0.102 Sat Jul 28 09:32 - crash (10:08) root tty1 Sat Jul 28 09:31 - crash (10:08) reboot system boot 3.10.0-514.el7.x Sat Jul 28 09:28 - 21:35 (12:06) root pts/0 192.168.0.102 Fri Jul 27 23:19 - crash (10:09) root tty1 Fri Jul 27 23:16 - crash (10:11) reboot system boot 3.10.0-514.el7.x Fri Jul 27 23:15 - 21:35 (22:19) root pts/0 192.168.1.102 Fri Jul 27 10:12 - down (07:37) root tty1 Fri Jul 27 10:10 - 17:49 (07:39) reboot system boot 3.10.0-514.el7.x Fri Jul 27 10:07 - 17:50 (07:42) root tty1 Thu Jul 26 22:17 - 22:37 (00:20) reboot system boot 3.10.0-514.el7.x Thu Jul 26 22:05 - 22:37 (00:32) root tty1 Thu Jul 26 21:09 - 22:11 (01:02) reboot system boot 3.10.0-514.el7.x Thu Jul 26 20:59 - 22:12 (01:12) root tty1 Sun Jul 22 22:54 - 21:05 (3+22:11) reboot system boot 3.10.0-514.el7.x Sun Jul 22 22:52 - 21:05 (3+22:13) root pts/2 192.168.0.100 Sun Jul 22 22:41 - down (00:03) root pts/1 192.168.0.100 Sun Jul 22 22:39 - down (00:06) root pts/1 192.168.0.100 Sun Jul 22 22:37 - 22:39 (00:01) root pts/0 192.168.0.100 Sun Jul 22 22:26 - down (00:18) root tty1 Sun Jul 22 22:08 - 22:45 (00:36) reboot system boot 3.10.0-514.el7.x Sun Jul 22 22:07 - 22:45 (00:37) root tty1 Sun Jul 22 16:32 - 22:06 (05:33) reboot system boot 3.10.0-514.el7.x Sun Jul 22 16:31 - 22:06 (05:35) root pts/0 192.168.0.25 Sun Jul 22 16:22 - crash (00:08) root tty1 Sun Jul 22 16:20 - crash (00:10) reboot system boot 3.10.0-514.el7.x Sun Jul 22 16:19 - 22:06 (05:46) root pts/0 192.168.0.100 Sun Jul 22 16:14 - 16:15 (00:00) root tty1 Sun Jul 22 16:11 - crash (00:08) reboot system boot 3.10.0-514.el7.x Sun Jul 22 16:10 - 22:06 (05:55) root pts/0 192.168.0.100 Sun Jul 22 13:32 - crash (02:37) root pts/0 192.168.0.100 Sun Jul 22 13:26 - 13:28 (00:01) root tty1 Sun Jul 22 12:06 - crash (04:03) reboot system boot 3.10.0-514.el7.x Sun Jul 22 11:57 - 22:06 (10:09) root pts/1 192.168.0.100 Sun Jul 22 11:54 - 11:55 (00:00) root pts/0 192.168.0.100 Sun Jul 22 11:52 - down (00:03) root tty1 Sun Jul 22 11:45 - 11:55 (00:09) reboot system boot 3.10.0-514.el7.x Sun Jul 22 11:44 - 11:55 (00:10) root pts/1 192.168.0.100 Sun Jul 22 11:30 - down (00:07) root pts/0 192.168.0.100 Sun Jul 22 11:23 - down (00:14) root tty1 Sun Jul 22 11:19 - 11:37 (00:17) reboot system boot 3.10.0-514.el7.x Sun Jul 22 11:18 - 11:37 (00:19) root tty1 Sun Jul 22 11:08 - 11:11 (00:02) reboot system boot 3.10.0-514.el7.x Sun Jul 22 11:07 - 11:11 (00:03) root pts/0 192.168.0.100 Sun Jul 22 11:03 - down (00:01) root tty1 Sun Jul 22 11:01 - 11:05 (00:03) reboot system boot 3.10.0-514.el7.x Sun Jul 22 10:57 - 11:05 (00:07) root pts/1 192.168.0.100 Sun Jul 22 10:44 - 10:55 (00:11) root pts/0 192.168.0.100 Sun Jul 22 10:37 - crash (00:20) root pts/1 192.168.0.100 Sat Jul 21 23:00 - 23:21 (00:21) root pts/0 192.168.0.100 Sat Jul 21 22:58 - 23:01 (00:02) root pts/1 192.168.0.100 Sat Jul 21 22:50 - 22:58 (00:08) root pts/0 192.168.0.100 Sat Jul 21 20:57 - 22:51 (01:54) root pts/0 192.168.0.105 Tue Jul 17 21:44 - 23:39 (01:54) root tty1 Tue Jul 17 21:43 - crash (4+13:14) reboot system boot 3.10.0-514.el7.x Tue Jul 17 21:40 - 11:05 (4+13:24) root pts/0 192.168.0.103 Mon Jul 16 20:47 - crash (1+00:53) root tty1 Mon Jul 16 20:41 - crash (1+00:59) reboot system boot 3.10.0-514.el7.x Mon Jul 16 20:35 - 11:05 (5+14:30) reboot system boot 3.10.0-514.el7.x Mon Jul 16 20:30 - 11:05 (5+14:35) root pts/1 192.168.0.102 Sun Jul 15 16:16 - 21:36 (05:20) root pts/0 192.168.0.102 Sun Jul 15 16:14 - 16:17 (00:02) root pts/0 192.168.0.102 Sun Jul 15 15:22 - 16:14 (00:51) root tty1 Sun Jul 15 15:22 - crash (1+05:07) reboot system boot 3.10.0-514.el7.x Sun Jul 15 15:11 - 11:05 (6+19:53) root pts/0 192.168.0.102 Sun Jul 15 11:53 - crash (03:17) root tty1 Sun Jul 15 11:53 - crash (03:18) reboot system boot 3.10.0-514.el7.x Sun Jul 15 11:51 - 11:05 (6+23:13) root pts/0 192.168.0.103 Sat Jul 14 16:00 - crash (19:51) root pts/0 192.168.0.102 Thu Jul 12 20:06 - 00:31 (04:25) root tty1 Thu Jul 12 20:05 - crash (2+15:46) reboot system boot 3.10.0-514.el7.x Thu Jul 12 20:04 - 11:05 (9+15:00) root pts/0 192.168.0.100 Thu Jul 5 20:18 - crash (6+23:46) root tty1 Thu Jul 5 20:17 - crash (6+23:47) reboot system boot 3.10.0-514.el7.x Thu Jul 5 20:15 - 11:05 (16+14:49) root pts/0 192.168.0.100 Mon Jul 2 20:34 - crash (2+23:41) root tty1 Mon Jul 2 20:34 - crash (2+23:41) reboot system boot 3.10.0-514.el7.x Mon Jul 2 20:31 - 11:05 (19+14:34) root pts/0 192.168.0.104 Sun Jul 1 16:10 - 22:58 (06:47) root tty1 Sun Jul 1 16:03 - crash (1+04:27) reboot system boot 3.10.0-514.el7.x Sun Jul 1 16:02 - 11:05 (20+19:02) root pts/0 192.168.0.102 Sat Jun 16 15:53 - 22:27 (1+06:34) root tty1 Sat Jun 16 15:53 - crash (15+00:09) reboot system boot 3.10.0-514.el7.x Sat Jun 16 15:39 - 11:05 (35+19:25) root pts/0 192.168.0.101 Sun Jun 10 14:03 - 22:37 (08:33) root tty1 Sun Jun 10 14:03 - crash (6+01:36) reboot system boot 3.10.0-514.el7.x Sun Jun 10 13:58 - 11:05 (41+21:07) root pts/0 192.168.0.101 Sat Jun 9 22:30 - 22:39 (00:09) root pts/0 192.168.0.101 Sat Jun 9 11:31 - 22:30 (10:59) root tty1 Sat Jun 9 11:29 - crash (1+02:28) reboot system boot 3.10.0-514.el7.x Sat Jun 9 11:28 - 11:05 (42+23:37) root tty1 Wed Jun 6 21:45 - crash (2+13:42) reboot