课程第10次

botang · 发表于 2019-4-28 10:46:13

sort 和uniq：

[root@station60 labs]# sort -n 1.txt
1
3
3
6
20

------------------------------------------

[root@station60 labs]# sort -n 1.txt | uniq  -c
   1 1
   2 3
   1 6
   1 20
------------------------

</blockquote></div><p>在二级命令处，进行多行标准输入：</p><p><div class="blockcode"><blockquote>#!/bin/sh
/u01/app/oracle/product/11.2.0/dbhome_1/bin/sqlplus <<-EOF
conn / as sysdba
startup
exit
EOF

复制代码

[root@station60 labs]# read -p "Please input the value of A: " A < 4.txt
[root@station60 labs]# echo $A
100
[root@station60 labs]# ls
1.txt 2.txt 3.txt 4.txt
[root@station60 labs]# ls
1.txt 2.txt 3.txt 4.txt
[root@station60 labs]# ls > 5.txt
[root@station60 labs]# cat 5.txt
1.txt
2.txt
3.txt
4.txt
5.txt
[root@station60 labs]# ls -l
total 20
-rw-r--r--. 1 root root 11 Apr 28 08:14 1.txt
-rw-r--r--. 1 root root 224 Apr 28 08:26 2.txt
-rw-r--r--. 1 root root 13 Apr 28 08:38 3.txt
-rw-r--r--. 1 root root 4 Apr 28 08:56 4.txt
-rw-r--r--. 1 root root 30 Apr 28 09:00 5.txt
[root@station60 labs]# ls
1.txt 2.txt 3.txt 4.txt 5.txt
[root@station60 labs]# read B < 5.txt
[root@station60 labs]# echo $B
1.txt
[root@station60 labs]# B=$(cat 5.txt)
[root@station60 labs]# echo $B
1.txt 2.txt 3.txt 4.txt 5.txt
[root@station60 labs]#

复制代码

注意空格：

[root@station60 labs]# ls 1.txt botang.txt >7.txt 2>&1
[root@station60 labs]# cat 7.txt
ls: cannot access botang.txt: No such file or directory
1.txt
[root@station60 labs]# ls 1.txt botang.txt &>8.txt
[root@station60 labs]# cat 8.txt
ls: cannot access botang.txt: No such file or directory
1.txt
[root@station60 labs]# ls 1.txt botang.txt & >9.txt
[1] 19920
[root@station60 labs]# ls: cannot access botang.txt: No such file or directory
1.txt
[1]+ Exit 2 ls --color=auto 1.txt botang.txt

复制代码

参考：

firewall-cmd --permanent --add-service=http
firewall-cmd --reload

复制代码

<VirtualHost *:80>
DocumentRoot /var/www/html/station60/
ServerName station60.example.com
CustomLog logs/station60.log combined
</VirtualHost>
<VirtualHost *:80>
DocumentRoot /var/www/html/www60/
ServerName www60.example.com
CustomLog logs/www60.log combined
</VirtualHost>

复制代码

/etc/named.conf:

# /etc/named.conf
#
# This file should be used for all classes except RH320.
# Replaces: named.conf-isolated, named.conf-internet
########################################################################
#
# Define the location of the zone files, clean daily,
# and possibly specify forwarders.
#
########################################################################
// Define ACL(s) here
acl exampleNetwork { 192.168.0.0/24; };
acl crackerNetwork { 192.168.1.0/24; };
acl internal { 127.0.0.1; 192.168.0.0/24; 192.168.1.0/24; };
acl bogusNets { 0.0.0.0/8;
1.0.0.0/8;
2.0.0.0/8;
192.0.2.0/24;
224.0.0.0/3;
10.0.0.0/8;
172.16.0.0/12;
};
options {
// Where do our zone files live?
directory "/var/named";
cleaning-interval 1440;
// Use the ACL to say who can query us
allow-query { internal; };
// Allow recursion for localnets( not really needed becauses of above )
allow-recursion { internal; };
// Allow zone transfers only to exampleNetwork ACL
allow-transfer { exampleNetwork; };
// Blackhole illegal addresses commonly used for spoofing
// This is also redundant but we are showing off
blackhole { bogusNets; };
// If you're behind a firewall but have Internet access, you
// might need to run DNS lookups through another name server
// that can see through it, to resolve outside hosts.
// The commented-out line below works for Meridian.
# forwarders { 192.168.22.250; };
// Get rid of annoying reminder of default that is, in fact, the
// opposite of what man named.conf would have you believe.
auth-nxdomain no;
};
// Magic to make rndc work
include "/etc/rndc.key";
controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
#########################################################################
#
# Help out root nameservers; take responsibility for localhost.
#
#########################################################################
// file names are arbitrary and can be anything
// RFC 1033 uses .zone in their examples and so shall we
zone "localhost" {
type master;
file "localhost.zone";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "127.0.0.zone";
};
########################################################################
#
# Provide a hint to the root nameservers
#
########################################################################
zone "." {
type hint;
file "named.ca";
};
#########################################################################
#
# Master nameserver for example.com and 192.168.0/24
#
#########################################################################
zone "example.com" {
type master;
file "example.com.zone";
// The forwarders line below turns off forwarding, if specified
// above, for delegated subdomains (domainXX.example.com, etc).
// (So we talk directly to the server for the zone we delegated,
// rather than asking the forwarder to do it for us.)
forwarders {};
};
zone "0.168.192.in-addr.arpa" {
type master;
file "192.168.0.zone";
forwarders {};
};
#########################################################################
#
# Master nameserver for cracker.org and 192.168.1/24
#
#########################################################################
zone "cracker.org" {
type master;
file "cracker.org.zone";
forwarders{};
};
zone "1.168.192.in-addr.arpa" {
type master;
file "192.168.1.zone";
forwarders{};
};
zone "something.net" {
type master;
file "something.net.zone";
// The forwarders line below turns off forwarding, if specified
// above, for delegated subdomains (domainXX.example.com, etc).
// (So we talk directly to the server for the zone we delegated,
// rather than asking the forwarder to do it for us.)
forwarders {};
};

复制代码

/var/named/chroot/var/named/example.com.zone:

; Specify the time-to-live( TTL ) for the zone
$TTL 86400 ; 1 Day ( we could have used 1D )
; Begin Start Of Authority resource record
example.com. IN SOA station90.example.com. root.station90.example.com. (
2003040100 ; serial number
1H ; refresh slave
5M ; retry query
1W ; expire
1M ; negative TTL
)
; Specify our name servers
; !!WARNING: You can not use CNAMEs for RDATA here !!
; owner TTL CL type RDATA
@ IN NS station90.example.com.
; Specify our mail exchangers
; !!WARNING: You can not use CNAMEs for RDATA here !!
; owner TTL CL type RDATA
@ IN MX 10 station90.example.com.
; This is broken and against RFC but must be done to placate the masses
; owner TTL CL type RDATA
example.com. IN A 192.168.0.90
; List our CNAME records ( aliases ) here
; owner TTL CL type RDATA
mail.example.com. 3600 IN CNAME server1.example.com.
kerberos.example.com. 3600 IN CNAME server1.example.com.
; List our A records ( hosts ) here
; owner TTL CL type RDATA
station1.example.com. IN A 192.168.0.1
station2 IN A 192.168.0.2
station3 IN A 192.168.0.3
station4 IN A 192.168.0.4
station5 IN A 192.168.0.5
station6 IN A 192.168.0.6
station7 IN A 192.168.0.7
station8 IN A 192.168.0.8
station9 IN A 192.168.0.9
station10 IN A 192.168.0.10
station11 IN A 192.168.0.11
station12 IN A 192.168.0.12
station13 IN A 192.168.0.13
station14 IN A 192.168.0.14
station15 IN A 192.168.0.15
station16 IN A 192.168.0.16
station17 IN A 192.168.0.17
station18 IN A 192.168.0.18
station19 IN A 192.168.0.19
station20 IN A 192.168.0.20
server1 IN A 192.168.0.254
; Okay, my fingers are getting tired. BIND 8.1 and BIND 9.1 and later supports
; a shortcut. $GENERATE creates a record for each value in the
; numerical range specified in the first argument, replacing any $
; in the template with the current value of the iterator.
; Set up the rest of the station records.
$GENERATE 21-100 station[ DISCUZ_CODE_9 ]nbsp; A 192.168.0.$
; Set up CNAMEs for www1.example.com and so on.
$GENERATE 1-100 www[ DISCUZ_CODE_28 ]nbsp; CNAME station$
; Delegate owner1.example.com and so on to the individual stations.
$GENERATE 1-100 domain$.example.com. NS station$.example.com.
$GENERATE 1-100 hierarchy$.example.com. NS station$.example.com.
; The $GENERATE shortcut is normally used to simplify delegating
; subnets on a non-octet boundary. (This is for non-traditional
; network sizes -- everything but /8, /16, and /24 subnets.)
; For the RHEL5.1 RH253 changes:
$GENERATE 101-200 server$.example.com. A 192.168.0.$
$GENERATE 101-200 domain$.example.com. NS server$.example.com.
$GENERATE 101-200 www[ DISCUZ_CODE_28 ]nbsp; CNAME server$

复制代码

/var/named/chroot/var/named/192.168.0.zone:

; Specify the time-to-live( TTL ) for the zone
$TTL 86400 ; 1 Day ( we could have used 1D )
; Begin Start Of Authority resource record
0.168.192.IN-ADDR.ARPA. IN SOA station90.example.com. root.station90.example.com.(
2003040100 ; serial number
1H ; refresh slave
5M ; retry query
1W ; expire
1M ; negative TTL
)
; Specify our name servers
; !!WARNING: You can not use CNAMEs for RDATA here !!
; owner TTL CL type RDATA
@ IN NS station90.example.com.
; List our PTR records ( rev lookup ) here
; owner TTL CL type RDATA
1.0.168.192.IN-ADDR.ARPA. IN PTR station1.example.com.
2 IN PTR station2.example.com.
3 IN PTR station3.example.com.
4 IN PTR station4.example.com.
5 IN PTR station5.example.com.
6 IN PTR station6.example.com.
7 IN PTR station7.example.com.
8 IN PTR station8.example.com.
9 IN PTR station9.example.com.
10 IN PTR station10.example.com.
11 IN PTR station11.example.com.
12 IN PTR station12.example.com.
13 IN PTR station13.example.com.
14 IN PTR station14.example.com.
15 IN PTR station15.example.com.
16 IN PTR station16.example.com.
17 IN PTR station17.example.com.
18 IN PTR station18.example.com.
19 IN PTR station19.example.com.
20 IN PTR station20.example.com.
21 IN PTR station21.example.com.
22 IN PTR station22.example.com.
23 IN PTR station23.example.com.
24 IN PTR station24.example.com.
25 IN PTR station25.example.com.
26 IN PTR station26.example.com.
27 IN PTR station27.example.com.
28 IN PTR station28.example.com.
29 IN PTR station29.example.com.
30 IN PTR station30.example.com.
31 IN PTR station31.example.com.
32 IN PTR station32.example.com.
33 IN PTR station33.example.com.
34 IN PTR station34.example.com.
35 IN PTR station35.example.com.
36 IN PTR station36.example.com.
37 IN PTR station37.example.com.
38 IN PTR station38.example.com.
39 IN PTR station39.example.com.
40 IN PTR station40.example.com.
41 IN PTR station41.example.com.
42 IN PTR station42.example.com.
43 IN PTR station43.example.com.
44 IN PTR station44.example.com.
45 IN PTR station45.example.com.
46 IN PTR station46.example.com.
47 IN PTR station47.example.com.
48 IN PTR station48.example.com.
49 IN PTR station49.example.com.
50 IN PTR station50.example.com.
51 IN PTR station51.example.com.
52 IN PTR station52.example.com.
53 IN PTR station53.example.com.
54 IN PTR station54.example.com.
55 IN PTR station55.example.com.
56 IN PTR station56.example.com.
57 IN PTR station57.example.com.
58 IN PTR station58.example.com.
59 IN PTR station59.example.com.
60 IN PTR station60.example.com.
61 IN PTR station61.example.com.
62 IN PTR station62.example.com.
63 IN PTR station63.example.com.
64 IN PTR station64.example.com.
65 IN PTR station65.example.com.
66 IN PTR station66.example.com.
67 IN PTR station67.example.com.
68 IN PTR station68.example.com.
69 IN PTR station69.example.com.
70 IN PTR station70.example.com.
71 IN PTR station71.example.com.
72 IN PTR station72.example.com.
73 IN PTR station73.example.com.
74 IN PTR station74.example.com.
75 IN PTR station75.example.com.
76 IN PTR station76.example.com.
77 IN PTR station77.example.com.
78 IN PTR station78.example.com.
79 IN PTR station79.example.com.
80 IN PTR station80.example.com.
81 IN PTR station81.example.com.
82 IN PTR station82.example.com.
83 IN PTR station83.example.com.
84 IN PTR station84.example.com.
85 IN PTR station85.example.com.
86 IN PTR station86.example.com.
87 IN PTR station87.example.com.
88 IN PTR station88.example.com.
89 IN PTR station89.example.com.
90 IN PTR station90.example.com.
91 IN PTR station91.example.com.
92 IN PTR station92.example.com.
93 IN PTR station93.example.com.
94 IN PTR station94.example.com.
95 IN PTR station95.example.com.
96 IN PTR station96.example.com.
97 IN PTR station97.example.com.
98 IN PTR station98.example.com.
99 IN PTR station99.example.com.
100 IN PTR station100.example.com.
; For the RHEL5.1 changes
101 IN PTR server101.example.com.
102 IN PTR server102.example.com.
103 IN PTR server103.example.com.
104 IN PTR server104.example.com.
105 IN PTR server105.example.com.
106 IN PTR server106.example.com.
107 IN PTR server107.example.com.
108 IN PTR server108.example.com.
109 IN PTR server109.example.com.
110 IN PTR server110.example.com.
111 IN PTR server111.example.com.
112 IN PTR server112.example.com.
113 IN PTR server113.example.com.
114 IN PTR server114.example.com.
115 IN PTR server115.example.com.
116 IN PTR server116.example.com.
117 IN PTR server117.example.com.
118 IN PTR server118.example.com.
119 IN PTR server119.example.com.
120 IN PTR server120.example.com.
121 IN PTR server121.example.com.
122 IN PTR server122.example.com.
123 IN PTR server123.example.com.
124 IN PTR server124.example.com.
125 IN PTR server125.example.com.
126 IN PTR server126.example.com.
127 IN PTR server127.example.com.
128 IN PTR server128.example.com.
129 IN PTR server129.example.com.
130 IN PTR server130.example.com.
131 IN PTR server131.example.com.
132 IN PTR server132.example.com.
133 IN PTR server133.example.com.
134 IN PTR server134.example.com.
135 IN PTR server135.example.com.
136 IN PTR server136.example.com.
137 IN PTR server137.example.com.
138 IN PTR server138.example.com.
139 IN PTR server139.example.com.
140 IN PTR server140.example.com.
141 IN PTR server141.example.com.
142 IN PTR server142.example.com.
143 IN PTR server143.example.com.
144 IN PTR server144.example.com.
145 IN PTR server145.example.com.
146 IN PTR server146.example.com.
147 IN PTR server147.example.com.
148 IN PTR server148.example.com.
149 IN PTR server149.example.com.
150 IN PTR server150.example.com.
151 IN PTR server151.example.com.
152 IN PTR server152.example.com.
153 IN PTR server153.example.com.
154 IN PTR server154.example.com.
155 IN PTR server155.example.com.
156 IN PTR server156.example.com.
157 IN PTR server157.example.com.
158 IN PTR server158.example.com.
159 IN PTR server159.example.com.
160 IN PTR server160.example.com.
161 IN PTR server161.example.com.
162 IN PTR server162.example.com.
163 IN PTR server163.example.com.
164 IN PTR server164.example.com.
165 IN PTR server165.example.com.
166 IN PTR server166.example.com.
167 IN PTR server167.example.com.
168 IN PTR server168.example.com.
169 IN PTR server169.example.com.
170 IN PTR server170.example.com.
171 IN PTR server171.example.com.
172 IN PTR server172.example.com.
173 IN PTR server173.example.com.
174 IN PTR server174.example.com.
175 IN PTR server175.example.com.
176 IN PTR server176.example.com.
177 IN PTR server177.example.com.
178 IN PTR server178.example.com.
179 IN PTR server179.example.com.
180 IN PTR server180.example.com.
181 IN PTR server181.example.com.
182 IN PTR server182.example.com.
183 IN PTR server183.example.com.
184 IN PTR server184.example.com.
185 IN PTR server185.example.com.
186 IN PTR server186.example.com.
187 IN PTR server187.example.com.
188 IN PTR server188.example.com.
189 IN PTR server189.example.com.
190 IN PTR server190.example.com.
191 IN PTR server191.example.com.
192 IN PTR server192.example.com.
193 IN PTR server193.example.com.
194 IN PTR server194.example.com.
195 IN PTR server195.example.com.
196 IN PTR server196.example.com.
197 IN PTR server197.example.com.
198 IN PTR server198.example.com.
199 IN PTR server199.example.com.
200 IN PTR server200.example.com.
254 IN PTR server1.example.com.
; Note that we're not actually delegating the students authority to
; manage their IP addresses...so their server and our server will
; disagree on the correct reverse lookup for their IP address, and
; we're both claiming to be authoritative. Naughty of us. :) We
; have to do this, since their server won't be there most of the
; time to delegate to. Doesn't matter for ownerXX.example.com.

复制代码