/l3/users/clint/nt-lNet/linux4.linux.nt/user :1 :2 :3 :4 :5 :6 :7 :8 :9 :10 :11 :12 :13 :14 :15 :16 :17 :18 |
|
#apt-get install bind9
![]() Настраивается пакет libisccfg1 (9.3.2-P1-1) ... Настраивается пакет bind9 (9.3.2-P1-1) ... wrote key file "/etc/bind/rndc.key" chgrp: невозможно получить доступ к `/etc/bind/named.conf*': No such file or directory dpkg: не удалось обработать параметр bind9 (--configure): подпроцесс post-installation script возвратил код ошибки 1 При обработке следующих пакетов произошли ошибки: bind9 E: Sub-process /usr/bin/dpkg returned an error code (1) BIND -Berkly Internet Name Domain |
#ls /etc/bind/
64 bytes from cluster1.hitfarm.com (64.40.102.44): icmp_seq=1 ttl=44 time=205 ms 64 bytes from cluster1.hitfarm.com (64.40.102.44): icmp_seq=2 ttl=44 time=213 ms 64 bytes from cluster1.hitfarm.com (64.40.102.44): icmp_seq=3 ttl=44 time=202 ms ^[64 bytes from cluster1.hitfarm.com (64.40.102.44): icmp_seq=4 ttl=44 time=239 ms 64 bytes from cluster1.hitfarm.com (64.40.102.44): icmp_seq=5 ttl=44 time=231 ms --- linux9.zlo.net ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4052ms rtt min/avg/max/mdev = 202.576/218.337/239.009/14.457 ms rndc.key |
#apt-get install bind9
Reading Package Lists... Done Building Dependency Tree... Done bind9 is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 797 not upgraded. 1 not fully installed or removed. Need to get 0B of archives. After unpacking 0B of additional disk space will be used. Настраивается пакет bind9 (9.3.2-P1-1) ... Starting domain name service...:. |
#ls /etc/bind/
rndc.key |
#apt-get -f install
Reading Package Lists... Done Building Dependency Tree... Done 0 upgraded, 0 newly installed, 0 to remove and 797 not upgraded. |
#apt-get --purge remove bind9
Reading Package Lists... Done Building Dependency Tree... Done The following packages will be REMOVED: bind9* 0 upgraded, 0 newly installed, 1 to remove and 797 not upgraded. Need to get 0B of archives. After unpacking 762kB disk space will be freed. Do you want to continue? [Y/n] (Чтение базы данных... на данный момент установлено 103703 файлов и каталогов.) Удаляется пакет bind9... Stopping domain name service...:rndc: connect failed: connection refused . Удаляются файлы конфигурации пакета bind9... |
#ls /etc/bind/
![]() ls: /etc/bind/: No such file or directory |
#apt-get install bind9
Reading Package Lists... Done Building Dependency Tree... Done Suggested packages: bind9-doc The following NEW packages will be installed: bind9 0 upgraded, 1 newly installed, 0 to remove and 797 not upgraded. Need to get 0B/285kB of archives. After unpacking 762kB of additional disk space will be used. Выбор ранее не выбранного пакета bind9. (Чтение базы данных... на данный момент установлено 103665 файлов и каталогов.) Распаковывается пакет bind9 (из файла .../bind9_1%3a9.3.2-P1-1_i386.deb)... Настраивается пакет bind9 (9.3.2-P1-1) ... wrote key file "/etc/bind/rndc.key" Starting domain name service...:. |
#ls /etc/bind/
db.0 db.127 db.255 db.empty db.local db.root named.conf named.conf.local named.conf.options rndc.key zones.rfc1918 |
#cd /etc/bind/
|
#vi named.conf.options
|
#/etc/init.d/bind9 restart
64 bytes from cluster1.hitfarm.com (64.40.102.44): icmp_seq=2 ttl=44 time=213 ms 64 bytes from cluster1.hitfarm.com (64.40.102.44): icmp_seq=3 ttl=44 time=202 ms ^[64 bytes from cluster1.hitfarm.com (64.40.102.44): icmp_seq=4 ttl=44 time=239 ms 64 bytes from cluster1.hitfarm.com (64.40.102.44): icmp_seq=5 ttl=44 time=231 ms --- linux9.zlo.net ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4052ms rtt min/avg/max/mdev = 202.576/218.337/239.009/14.457 ms Stopping domain name service...:. Starting domain name service...:. |
#tail /var/log/daemon.log
rtt min/avg/max/mdev = 202.576/218.337/239.009/14.457 ms Sep 20 16:32:42 linux4 named[22297]: no IPv6 interfaces found Sep 20 16:32:42 linux4 named[22297]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 20 16:32:42 linux4 named[22297]: listening on IPv4 interface eth0, 192.168.15.4#53 Sep 20 16:32:42 linux4 named[22297]: listening on IPv4 interface eth1, 192.168.16.1#53 Sep 20 16:32:42 linux4 named[22297]: command channel listening on 127.0.0.1#953 Sep 20 16:32:42 linux4 named[22297]: zone 0.in-addr.arpa/IN: loaded serial 1 Sep 20 16:32:42 linux4 named[22297]: zone 127.in-addr.arpa/IN: loaded serial 1 Sep 20 16:32:42 linux4 named[22297]: zone 255.in-addr.arpa/IN: loaded serial 1 Sep 20 16:32:42 linux4 named[22297]: zone localhost/IN: loaded serial 1 Sep 20 16:32:42 linux4 named[22297]: running |
#netstat -lnp | grep :53
--- linux9.zlo.net ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4052ms rtt min/avg/max/mdev = 202.576/218.337/239.009/14.457 ms tcp 0 0 192.168.16.1:53 0.0.0.0:* LISTEN 22297/named tcp 0 0 192.168.15.4:53 0.0.0.0:* LISTEN 22297/named tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 22297/named tcp 0 0 0.0.0.0:53535 0.0.0.0:* LISTEN 21575/licq udp 0 0 192.168.16.1:53 0.0.0.0:* 22297/named udp 0 0 192.168.15.4:53 0.0.0.0:* 22297/named udp 0 0 127.0.0.1:53 0.0.0.0:* 22297/named |
#dig @127.0.0.1 mail.ru
mail.ru. 4411 IN NS ns5.mail.ru. ;; ADDITIONAL SECTION: ns.mail.ru. 17697 IN A 194.67.23.130 ns5.mail.ru. 17716 IN A 194.67.23.232 ;; Query time: 23 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Sep 20 16:33:25 2006 ;; MSG SIZE rcvd: 180 |
#dig @127.0.0.1 mail.ru ns
; <<>> DiG 9.2.4 <<>> @127.0.0.1 mail.ru ns ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18011 ;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 2 ;; QUESTION SECTION: ;mail.ru. IN NS ;; ANSWER SECTION: mail.ru. 4408 IN NS ns1.mail.ru. mail.ru. 4408 IN NS ns2.mail.ru. mail.ru. 4408 IN NS ns3.mail.ru. mail.ru. 4408 IN NS ns4.mail.ru. mail.ru. 4408 IN NS ns5.mail.ru. mail.ru. 4408 IN NS ns.mail.ru. ;; ADDITIONAL SECTION: ns.mail.ru. 17694 IN A 194.67.23.130 ns5.mail.ru. 17713 IN A 194.67.23.232 ;; Query time: 18 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Sep 20 16:33:28 2006 ;; MSG SIZE rcvd: 164 |
#vi /etc/resolv.conf
|
#dig @ns1.mail.ru ya.ru a
; <<>> DiG 9.2.4 <<>> @ns1.mail.ru ya.ru a ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53161 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;ya.ru. IN A ;; AUTHORITY SECTION: ya.ru. 3877 IN NS ns1.yandex.ru. ya.ru. 3877 IN NS ns2.yandex.ru. ya.ru. 3877 IN NS ns3.yandex.ru. ya.ru. 3877 IN NS ns.ispm.ru. ;; ADDITIONAL SECTION: ns1.yandex.ru. 56557 IN A 213.180.193.1 ns2.yandex.ru. 56557 IN A 213.180.199.34 ns3.yandex.ru. 5616 IN A 213.180.193.2 ns.ispm.ru. 81101 IN A 80.244.228.2 ;; Query time: 98 msec ;; SERVER: 194.67.57.103#53(ns1.mail.ru) ;; WHEN: Wed Sep 20 16:36:00 2006 ;; MSG SIZE rcvd: 170 |
#vi named.conf.options
|
#cat named.conf.options
// the all-0's placeholder. forwarders { 192.168.15.254; }; //Передавать запрос на 192.168.15.254 если не в силах его обработать сам! // Для использования зоны линукс.нт - в инете ее нет !! auth-nxdomain no; # conform to RFC1035 }; |
#rndc dumpdb
PING linux9.zlo.net (64.40.102.44) 56(84) bytes of data. 64 bytes from cluster1.hitfarm.com (64.40.102.44): icmp_seq=1 ttl=44 time=205 ms 64 bytes from cluster1.hitfarm.com (64.40.102.44): icmp_seq=2 ttl=44 time=213 ms 64 bytes from cluster1.hitfarm.com (64.40.102.44): icmp_seq=3 ttl=44 time=202 ms ^[64 bytes from cluster1.hitfarm.com (64.40.102.44): icmp_seq=4 ttl=44 time=239 ms 64 bytes from cluster1.hitfarm.com (64.40.102.44): icmp_seq=5 ttl=44 time=231 ms --- linux9.zlo.net ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4052ms rtt min/avg/max/mdev = 202.576/218.337/239.009/14.457 ms |
#less /var/cache/bind/named_dump.db
|
#grep -v '^;' /var/cache/bind/named_dump.db | less
|
#rndc
![]() Usage: rndc [-c config] [-s server] [-p port] [-k key-file ] [-y key] [-V] command command is one of the following: reload Reload configuration file and zones. reload zone [class [view]] Reload a single zone. refresh zone [class [view]] Schedule immediate maintenance for a zone. retransfer zone [class [view]] Retransfer a single zone without checking serial number. ... notrace Set debugging level to 0. flush Flushes all of the server's caches. flush [view] Flushes the server's cache for a view. flushname name [view] Flush the given name from the server's cache(s) status Display status of the server. recursing Dump the queries that are currently recursing (named.recursing) *restart Restart the server. * == not yet implemented Version: 9.3.2-P1 |
#rndc stats
|
#less /var/cache/bind/named
![]() |
#less /var/cache/bind/named.stats
|
#less /var/cache/bind/named.stats
|
#vi named.conf
|
#vi named.conf.options
|
#/etc/init.d/bind9 restart]
![]() Usage: /etc/init.d/bind9 {start|stop|reload|restart|force-reload}. |
#/etc/init.d/bind9 restart
Stopping domain name service...:. Starting domain name service...:. |
#tail /var/log/daemon.log
Sep 20 16:50:58 linux4 named[22533]: found 1 CPU, using 1 worker thread Sep 20 16:50:58 linux4 named[22533]: loading configuration from '/etc/bind/named.conf' Sep 20 16:50:58 linux4 named[22533]: no IPv6 interfaces found Sep 20 16:50:58 linux4 named[22533]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 20 16:50:58 linux4 named[22533]: command channel listening on 127.0.0.1#953 Sep 20 16:50:58 linux4 named[22533]: zone 0.in-addr.arpa/IN: loaded serial 1 Sep 20 16:50:58 linux4 named[22533]: zone 127.in-addr.arpa/IN: loaded serial 1 Sep 20 16:50:58 linux4 named[22533]: zone 255.in-addr.arpa/IN: loaded serial 1 Sep 20 16:50:58 linux4 named[22533]: zone localhost/IN: loaded serial 1 Sep 20 16:50:58 linux4 named[22533]: running |
#vi named.conf.options
|
#cat named.conf.options
options { directory "/var/cache/bind"; // If there is a firewall between you and nameservers you want // to talk to, you might need to uncomment the query-source // directive below. Previous versions of BIND always asked // questions using port 53, but BIND 8.1 and later use an unprivileged // port by default. // query-source address * port 53; // If your ISP provided one or more IP addresses for stable // nameservers, you probably want to use them as forwarders. ... allow-query { 127.0.0.1; 192.168.15.0/24; }; //Привязка к определенным интерфейсам listen-on { 192.168.15.2; 127.0.0.1; }; }; |
#/etc/init.d/bind9 restart
Stopping domain name service...:. Starting domain name service...:. |
#tail /var/log/daemon.log
Sep 20 16:52:24 linux4 named[22599]: found 1 CPU, using 1 worker thread Sep 20 16:52:24 linux4 named[22599]: loading configuration from '/etc/bind/named.conf' Sep 20 16:52:24 linux4 named[22599]: no IPv6 interfaces found Sep 20 16:52:24 linux4 named[22599]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 20 16:52:24 linux4 named[22599]: command channel listening on 127.0.0.1#953 Sep 20 16:52:24 linux4 named[22599]: zone 0.in-addr.arpa/IN: loaded serial 1 Sep 20 16:52:24 linux4 named[22599]: zone 127.in-addr.arpa/IN: loaded serial 1 Sep 20 16:52:24 linux4 named[22599]: zone 255.in-addr.arpa/IN: loaded serial 1 Sep 20 16:52:24 linux4 named[22599]: zone localhost/IN: loaded serial 1 Sep 20 16:52:24 linux4 named[22599]: running |
#tail named.conf.options
}; //Привязка к определенным интерфейсам listen-on { 192.168.15.2; 127.0.0.1; }; }; |
#ls
db.0 db.127 db.255 db.empty db.local db.root named.conf named.conf.local named.conf.options rndc.key zones.rfc1918 |
#мvi named.conf
53 }; 54 }; 55 56 57 // From the release notes: 58 // Because many of our users are uncomfortable receiving undelegated answers 59 // from root or top level domains, other than a few for whom that behaviour 60 // has been trusted and expected for quite some length of time, we have now 61 // introduced the "root-delegations-only" feature which applies delegation-only 62 // logic to all top level domains, and to the root domain. An exception list 63 // should be specified, including "MUSEUM" and "DE", and any other top level "named.conf" 67L, 1787C записано |
#сcat named.conf
// This is the primary configuration file for the BIND DNS server named. // // Please read /usr/share/doc/bind9/README.Debian.gz for information on the // structure of BIND configuration files in Debian, *BEFORE* you customize // this configuration file. // // If you are just adding zones, please do that in /etc/bind/named.conf.local include "/etc/bind/named.conf.options"; // prime the server with knowledge of the root servers zone "." { ... // From the release notes: // Because many of our users are uncomfortable receiving undelegated answers // from root or top level domains, other than a few for whom that behaviour // has been trusted and expected for quite some length of time, we have now // introduced the "root-delegations-only" feature which applies delegation-only // logic to all top level domains, and to the root domain. An exception list // should be specified, including "MUSEUM" and "DE", and any other top level // domains from whom undelegated responses are expected and trusted. // root-delegation-only exclude { "DE"; "MUSEUM"; }; include "/etc/bind/named.conf.local"; |
#cat /etc/bind/named.conf
// This is the primary configuration file for the BIND DNS server named. // // Please read /usr/share/doc/bind9/README.Debian.gz for information on the // structure of BIND configuration files in Debian, *BEFORE* you customize // this configuration file. // // If you are just adding zones, please do that in /etc/bind/named.conf.local include "/etc/bind/named.conf.options"; // prime the server with knowledge of the root servers zone "." { ... // From the release notes: // Because many of our users are uncomfortable receiving undelegated answers // from root or top level domains, other than a few for whom that behaviour // has been trusted and expected for quite some length of time, we have now // introduced the "root-delegations-only" feature which applies delegation-only // logic to all top level domains, and to the root domain. An exception list // should be specified, including "MUSEUM" and "DE", and any other top level // domains from whom undelegated responses are expected and trusted. // root-delegation-only exclude { "DE"; "MUSEUM"; }; include "/etc/bind/named.conf.local"; |
#cat /etc/bind/named.conf
// This is the primary configuration file for the BIND DNS server named. // // Please read /usr/share/doc/bind9/README.Debian.gz for information on the // structure of BIND configuration files in Debian, *BEFORE* you customize // this configuration file. // // If you are just adding zones, please do that in /etc/bind/named.conf.local include "/etc/bind/named.conf.options"; // prime the server with knowledge of the root servers zone "." { ... // From the release notes: // Because many of our users are uncomfortable receiving undelegated answers // from root or top level domains, other than a few for whom that behaviour // has been trusted and expected for quite some length of time, we have now // introduced the "root-delegations-only" feature which applies delegation-only // logic to all top level domains, and to the root domain. An exception list // should be specified, including "MUSEUM" and "DE", and any other top level // domains from whom undelegated responses are expected and trusted. // root-delegation-only exclude { "DE"; "MUSEUM"; }; include "/etc/bind/named.conf.local"; |
#vi named.conf
|
#vi named.conf
|
#cat /etc/bind/named.conf
// This is the primary configuration file for the BIND DNS server named. // // Please read /usr/share/doc/bind9/README.Debian.gz for information on the // structure of BIND configuration files in Debian, *BEFORE* you customize // this configuration file. // // If you are just adding zones, please do that in /etc/bind/named.conf.local include "/etc/bind/named.conf.options"; // prime the server with knowledge of the root servers zone "." { ... // From the release notes: // Because many of our users are uncomfortable receiving undelegated answers // from root or top level domains, other than a few for whom that behaviour // has been trusted and expected for quite some length of time, we have now // introduced the "root-delegations-only" feature which applies delegation-only // logic to all top level domains, and to the root domain. An exception list // should be specified, including "MUSEUM" and "DE", and any other top level // domains from whom undelegated responses are expected and trusted. // root-delegation-only exclude { "DE"; "MUSEUM"; }; include "/etc/bind/named.conf.local"; |
#vi named.conf
|
#vi db.sergey.unix.nt
![]() |
#cat db.sergey.unix.nt
@ SOA yellow.sergey.unix.nt. hostmaster.sergey.unix.nt. ( 2006092001 10h 1h 1w 3h) NS yellow.sergey.unix.nt. ; NS yellow --> То же самое! yellow A 192.168.15.4 blue A 192.168.15.99 |
#tail /var/log/daemon.log
Sep 20 17:17:02 linux4 named[22849]: no IPv6 interfaces found Sep 20 17:17:02 linux4 named[22849]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 20 17:17:02 linux4 named[22849]: command channel listening on 127.0.0.1#953 Sep 20 17:17:02 linux4 named[22849]: zone 0.in-addr.arpa/IN: loaded serial 1 Sep 20 17:17:02 linux4 named[22849]: zone 127.in-addr.arpa/IN: loaded serial 1 Sep 20 17:17:02 linux4 named[22849]: zone 255.in-addr.arpa/IN: loaded serial 1 Sep 20 17:17:02 linux4 named[22849]: zone localhost/IN: loaded serial 1 Sep 20 17:17:02 linux4 named[22849]: /etc/bind/db.sergey.unix.nt:1: no TTL specified; using SOA MINTTL instead Sep 20 17:17:02 linux4 named[22849]: zone sergey.unix.nt/IN: loaded serial 2006092001 Sep 20 17:17:02 linux4 named[22849]: running |
#less /var/log/messages
|
#tail /var/log/daemon.log
Sep 20 17:17:02 linux4 named[22849]: no IPv6 interfaces found Sep 20 17:17:02 linux4 named[22849]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 20 17:17:02 linux4 named[22849]: command channel listening on 127.0.0.1#953 Sep 20 17:17:02 linux4 named[22849]: zone 0.in-addr.arpa/IN: loaded serial 1 Sep 20 17:17:02 linux4 named[22849]: zone 127.in-addr.arpa/IN: loaded serial 1 Sep 20 17:17:02 linux4 named[22849]: zone 255.in-addr.arpa/IN: loaded serial 1 Sep 20 17:17:02 linux4 named[22849]: zone localhost/IN: loaded serial 1 Sep 20 17:17:02 linux4 named[22849]: /etc/bind/db.sergey.unix.nt:1: no TTL specified; using SOA MINTTL instead Sep 20 17:17:02 linux4 named[22849]: zone sergey.unix.nt/IN: loaded serial 2006092001 Sep 20 17:17:02 linux4 named[22849]: running |
#vi db.sergey.unix.nt
|
#/etc/init.d/bind9 restart
Stopping domain name service...:. Starting domain name service...:. |
#tail /var/log/daemon.log
Sep 20 17:18:29 linux4 named[22922]: loading configuration from '/etc/bind/named.conf' Sep 20 17:18:29 linux4 named[22922]: no IPv6 interfaces found Sep 20 17:18:29 linux4 named[22922]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 20 17:18:29 linux4 named[22922]: command channel listening on 127.0.0.1#953 Sep 20 17:18:29 linux4 named[22922]: zone 0.in-addr.arpa/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone 127.in-addr.arpa/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone 255.in-addr.arpa/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone localhost/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone sergey.unix.nt/IN: loaded serial 2006092001 Sep 20 17:18:29 linux4 named[22922]: running |
#dig google.com mx
; <<>> DiG 9.2.4 <<>> google.com mx ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2572 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 4, ADDITIONAL: 8 ;; QUESTION SECTION: ;google.com. IN MX ;; ANSWER SECTION: google.com. 3600 IN MX 10 smtp1.google.com. google.com. 3600 IN MX 10 smtp2.google.com. ... smtp3.google.com. 600 IN A 64.233.183.25 smtp4.google.com. 600 IN A 66.102.9.25 ns1.google.com. 145661 IN A 216.239.32.10 ns2.google.com. 145659 IN A 216.239.34.10 ns3.google.com. 145659 IN A 216.239.36.10 ns4.google.com. 145661 IN A 216.239.38.10 ;; Query time: 182 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Sep 20 17:19:48 2006 ;; MSG SIZE rcvd: 316 |
#cat /etc/bind/db.sergey.unix.nt
10h 1h 1w 3h) NS yellow.sergey.unix.nt. ; NS yellow --> То же самое! yellow A 192.168.15.4 blue A 192.168.15.99 |
#cat /etc/bind/db.sergey.unix.nt
10h 1h 1w 3h) NS yellow.sergey.unix.nt. ; NS yellow --> То же самое! yellow A 192.168.15.4 blue A 192.168.15.99 |
#host yellow.sergey.unix.nt
yellow.sergey.unix.nt has address 192.168.15.4 |
#scp cherep@192.168.15.254:/etc/bind/named.conf /tmp/named.conf_linux
Password: named.conf 100% 3254 3.2KB/s 00:00 |
#host blue.sergey.unix.nt
blue.sergey.unix.nt has address 192.168.15.99 |
#tail /var/log/daemon.log
Sep 20 17:18:29 linux4 named[22922]: loading configuration from '/etc/bind/named.conf' Sep 20 17:18:29 linux4 named[22922]: no IPv6 interfaces found Sep 20 17:18:29 linux4 named[22922]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 20 17:18:29 linux4 named[22922]: command channel listening on 127.0.0.1#953 Sep 20 17:18:29 linux4 named[22922]: zone 0.in-addr.arpa/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone 127.in-addr.arpa/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone 255.in-addr.arpa/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone localhost/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone sergey.unix.nt/IN: loaded serial 2006092001 Sep 20 17:18:29 linux4 named[22922]: running |
#cat /etc/bind/db.sergey.unix.nt
$TTL 1d @ SOA yellow.sergey.unix.nt. hostmaster.sergey.unix.nt. ( 2006092001 10h 1h 1w 3h) NS yellow.sergey.unix.nt. ; NS yellow --> То же самое! yellow A 192.168.15.4 blue A 192.168.15.99 |
#tail /var/log/daemon.log
Sep 20 17:18:29 linux4 named[22922]: loading configuration from '/etc/bind/named.conf' Sep 20 17:18:29 linux4 named[22922]: no IPv6 interfaces found Sep 20 17:18:29 linux4 named[22922]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 20 17:18:29 linux4 named[22922]: command channel listening on 127.0.0.1#953 Sep 20 17:18:29 linux4 named[22922]: zone 0.in-addr.arpa/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone 127.in-addr.arpa/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone 255.in-addr.arpa/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone localhost/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone sergey.unix.nt/IN: loaded serial 2006092001 Sep 20 17:18:29 linux4 named[22922]: running |
#dig @sergey.unix.nt yellow.sergey.unix.nt.
![]() dig: Couldn't find server 'sergey.unix.nt': Name or service not known |
#dig @127.0.0.1 sergey.unix.nt.
; <<>> DiG 9.2.4 <<>> @127.0.0.1 sergey.unix.nt. ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39127 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;sergey.unix.nt. IN A ;; AUTHORITY SECTION: sergey.unix.nt. 10800 IN SOA yellow.sergey.unix.nt. hostmaster.sergey.unix.nt. 2006092001 36000 3600 604800 10800 ;; Query time: 16 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Sep 20 17:27:32 2006 ;; MSG SIZE rcvd: 86 |
#tail /var/log/daemon.log
Sep 20 17:18:29 linux4 named[22922]: loading configuration from '/etc/bind/named.conf' Sep 20 17:18:29 linux4 named[22922]: no IPv6 interfaces found Sep 20 17:18:29 linux4 named[22922]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 20 17:18:29 linux4 named[22922]: command channel listening on 127.0.0.1#953 Sep 20 17:18:29 linux4 named[22922]: zone 0.in-addr.arpa/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone 127.in-addr.arpa/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone 255.in-addr.arpa/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone localhost/IN: loaded serial 1 Sep 20 17:18:29 linux4 named[22922]: zone sergey.unix.nt/IN: loaded serial 2006092001 Sep 20 17:18:29 linux4 named[22922]: running |
#tail /var/log/messages
Sep 20 14:21:35 linux4 -- MARK -- Sep 20 14:41:35 linux4 -- MARK -- Sep 20 15:01:35 linux4 -- MARK -- Sep 20 15:21:36 linux4 -- MARK -- Sep 20 15:41:36 linux4 -- MARK -- Sep 20 16:01:36 linux4 -- MARK -- Sep 20 16:21:36 linux4 -- MARK -- Sep 20 16:41:37 linux4 -- MARK -- Sep 20 17:01:37 linux4 -- MARK -- Sep 20 17:21:37 linux4 -- MARK -- |
#less /var/log/messages
|
#less /var/log/daemon.log
|
#/etc/init.d/bind9 restart
Stopping domain name service...:. Starting domain name service...:. |
#less /var/log/daemon.log
|
#dig @127.0.0.1 sergey.unix.nt.
; <<>> DiG 9.2.4 <<>> @127.0.0.1 sergey.unix.nt. ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62464 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;sergey.unix.nt. IN A ;; AUTHORITY SECTION: sergey.unix.nt. 10800 IN SOA yellow.sergey.unix.nt. hostmaster.sergey.unix.nt. 2006092001 36000 3600 604800 10800 ;; Query time: 16 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Sep 20 17:29:24 2006 ;; MSG SIZE rcvd: 86 |
#dig @127.0.0.1 sergey.unix.nt
; <<>> DiG 9.2.4 <<>> @127.0.0.1 sergey.unix.nt ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51437 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;sergey.unix.nt. IN A ;; AUTHORITY SECTION: sergey.unix.nt. 10800 IN SOA yellow.sergey.unix.nt. hostmaster.sergey.unix.nt. 2006092001 36000 3600 604800 10800 ;; Query time: 17 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Sep 20 17:29:29 2006 ;; MSG SIZE rcvd: 86 |
#less /var/log/daemon.log
|
#host yellow.sergey.unix.nt
yellow.sergey.unix.nt has address 192.168.15.4 |
#host blue.sergey.unix.nt
blue.sergey.unix.nt has address 192.168.15.99 |
#dig @127.0.0.1 sergey.unix.nt.ÑÐ
![]() |
#vi db.sergey.unix.nt
|
#tail /var/log/daemon.log
![]() |
#vi db.sergey.unix.nt
|
#vi named.conf
|
#vi named.conf.options
|
#/etc/init.d/bind9 restart
Stopping domain name service...:. Starting domain name service...:. |
#scp cherep@192.168.15.254:/etc/bind/db.linux.nt /tmp
Password: db.linux.nt 100% 18KB 18.0KB/s 00:00 |
#cat /tmp/db.linux.nt
;c2.pasha A 192.168.16.162 ;pasha NS c1.pasha ; NS c2.pasha ; ;linux12 A 192.168.16.162 ;;linux12 NS linux12 ; ;pc1.olga A 192.168.16.4 ;olga NS pc1.olga ; ... linux243 A 192.168.15.243 linux244 A 192.168.15.244 linux245 A 192.168.15.245 linux246 A 192.168.15.246 linux247 A 192.168.15.247 linux248 A 192.168.15.248 linux249 A 192.168.15.249 linux250 A 192.168.15.250 linux251 A 192.168.15.251 linux252 A 192.168.15.252 |
#cat /tmp/db.linux.nt
;c2.pasha A 192.168.16.162 ;pasha NS c1.pasha ; NS c2.pasha ; ;linux12 A 192.168.16.162 ;;linux12 NS linux12 ; ;pc1.olga A 192.168.16.4 ;olga NS pc1.olga ; ... linux243 A 192.168.15.243 linux244 A 192.168.15.244 linux245 A 192.168.15.245 linux246 A 192.168.15.246 linux247 A 192.168.15.247 linux248 A 192.168.15.248 linux249 A 192.168.15.249 linux250 A 192.168.15.250 linux251 A 192.168.15.251 linux252 A 192.168.15.252 |
$ыsu -
Password: l3-agent is already running: pid=4645; pidfile=/root/.lilalo/l3-agent.pid После настройки локальной - в зоне linux.nt - sergey NS yellow.sergey и следуюшая строка yellow.sergey A 192.168.15.4 |
#cat /tmp/db.linux.nt
;c2.pasha A 192.168.16.162 ;pasha NS c1.pasha ; NS c2.pasha ; ;linux12 A 192.168.16.162 ;;linux12 NS linux12 ; ;pc1.olga A 192.168.16.4 ;olga NS pc1.olga ; ... linux243 A 192.168.15.243 linux244 A 192.168.15.244 linux245 A 192.168.15.245 linux246 A 192.168.15.246 linux247 A 192.168.15.247 linux248 A 192.168.15.248 linux249 A 192.168.15.249 linux250 A 192.168.15.250 linux251 A 192.168.15.251 linux252 A 192.168.15.252 |
#пgrep -v '^;' /tmp/db.linux.nt > /tmp/db.linux.nt2
|
#cat /tmp/db.linux.nt2
linux1 A 192.168.15.1 linux2 A 192.168.15.2 linux3 A 192.168.15.3 linux4 A 192.168.15.4 linux5 A 192.168.15.5 linux6 A 192.168.15.6 linux7 A 192.168.15.7 linux8 A 192.168.15.8 linux9 A 192.168.15.9 linux10 A 192.168.15.10 ... linux243 A 192.168.15.243 linux244 A 192.168.15.244 linux245 A 192.168.15.245 linux246 A 192.168.15.246 linux247 A 192.168.15.247 linux248 A 192.168.15.248 linux249 A 192.168.15.249 linux250 A 192.168.15.250 linux251 A 192.168.15.251 linux252 A 192.168.15.252 |
#cat /tmp/db.linux.nt2
linux1 A 192.168.15.1 linux2 A 192.168.15.2 linux3 A 192.168.15.3 linux4 A 192.168.15.4 linux5 A 192.168.15.5 linux6 A 192.168.15.6 linux7 A 192.168.15.7 linux8 A 192.168.15.8 linux9 A 192.168.15.9 linux10 A 192.168.15.10 ... linux243 A 192.168.15.243 linux244 A 192.168.15.244 linux245 A 192.168.15.245 linux246 A 192.168.15.246 linux247 A 192.168.15.247 linux248 A 192.168.15.248 linux249 A 192.168.15.249 linux250 A 192.168.15.250 linux251 A 192.168.15.251 linux252 A 192.168.15.252 |
#cat /tmp/db.linux.nt
![]() db.linux.nt db.linux.nt2 |
#vi /tmp/db.linux.nt2
|
#head -25 /tmp/db.linux.nt2
$TTL 3000h @ SOA linux.nt. imchubin.nt.com.ua. 2004050801 ( 10h ; slave-server connection period 1h ; retry 1w ; lifetime 1h ) ; negative ttl NS @ A 10.0.35.1 herz A 10.0.35.1 lav NS server2.lav server2.lav A 192.168.15.21 yuriksat NS yuriksat.yuriksat yuriksat.yuriksat A 192.168.15.2 sergey NS yellow.sergey yellow.sergey A 192.168.15.4 debian NS debian.debian debian.debian A 192.168.15.3 |
#head -25 /tmp/db.linux.nt2 > /tmp/db.linux.nt3
|
#cat /tmp/db.linux.nt3
$TTL 3000h @ SOA linux.nt. imchubin.nt.com.ua. 2004050801 ( 10h ; slave-server connection period 1h ; retry 1w ; lifetime 1h ) ; negative ttl NS @ A 10.0.35.1 herz A 10.0.35.1 lav NS server2.lav server2.lav A 192.168.15.21 yuriksat NS yuriksat.yuriksat yuriksat.yuriksat A 192.168.15.2 sergey NS yellow.sergey yellow.sergey A 192.168.15.4 debian NS debian.debian debian.debian A 192.168.15.3 |
$TTL 1d @ SOA yellow.sergey.unix.nt. hostmaster.sergey.unix.nt. ( 2006092001 10h 1h 1w 3h) NS yellow.sergey.unix.nt. ; NS yellow --> То же самое! yellow A 192.168.15.4 blue A 192.168.15.99
// This is the primary configuration file for the BIND DNS server named. // // Please read /usr/share/doc/bind9/README.Debian.gz for information on the // structure of BIND configuration files in Debian, *BEFORE* you customize // this configuration file. // // If you are just adding zones, please do that in /etc/bind/named.conf.local include "/etc/bind/named.conf.options"; // prime the server with knowledge of the root servers zone "." { type hint; file "/etc/bind/db.root"; }; // be authoritative for the localhost forward and reverse zones, and for // broadcast zones as per RFC 1912 zone "localhost" { type master; file "/etc/bind/db.local"; }; zone "127.in-addr.arpa" { type master; file "/etc/bind/db.127"; }; zone "0.in-addr.arpa" { type master; file "/etc/bind/db.0"; }; zone "255.in-addr.arpa" { type master; file "/etc/bind/db.255"; }; // zone "com" { type delegation-only; }; // zone "net" { type delegation-only; }; zone "sergey.unix.nt" { type master; file "/etc/bind/db.sergey.unix.nt"; //Чьи запросы обрабатывать? allow-query { 0.0.0.0/0; //Всем! //Или any; }; //Кто может скачивать зону sergey.unix.nt? allow-transfer { 127.0.0.1; }; }; // From the release notes: // Because many of our users are uncomfortable receiving undelegated answers // from root or top level domains, other than a few for whom that behaviour // has been trusted and expected for quite some length of time, we have now // introduced the "root-delegations-only" feature which applies delegation-only // logic to all top level domains, and to the root domain. An exception list // should be specified, including "MUSEUM" and "DE", and any other top level // domains from whom undelegated responses are expected and trusted. // root-delegation-only exclude { "DE"; "MUSEUM"; }; include "/etc/bind/named.conf.local";
db.linux.nt db.linux.nt2
linux1 A 192.168.15.1 linux2 A 192.168.15.2 linux3 A 192.168.15.3 linux4 A 192.168.15.4 linux5 A 192.168.15.5 linux6 A 192.168.15.6 linux7 A 192.168.15.7 linux8 A 192.168.15.8 linux9 A 192.168.15.9 linux10 A 192.168.15.10 linux11 A 192.168.15.11 linux12 A 192.168.15.12 linux13 A 192.168.15.13 linux14 A 192.168.15.14 linux15 A 192.168.15.15 linux16 A 192.168.15.16 linux17 A 192.168.15.17 linux18 A 192.168.15.18 linux19 A 192.168.15.19 uw1 A 192.168.15.31 uw2 A 192.168.16.62 uw3 A 192.168.16.126 win1 A 192.168.15.101 win2 A 192.168.15.102 win3 A 192.168.15.103 win4 A 192.168.15.104 win5 A 192.168.15.105 win6 A 192.168.15.106 win7 A 192.168.15.107 win8 A 192.168.15.108 win9 A 192.168.15.109 win10 A 192.168.15.110 win11 A 192.168.15.111 win12 A 192.168.15.112 win13 A 192.168.15.113 win14 A 192.168.15.114 win15 A 192.168.15.115 win16 A 192.168.15.116 win17 A 192.168.15.117 win18 A 192.168.15.118 win19 A 192.168.15.119 fbsd1 A 192.168.15.21 fbsd2 A 192.168.15.22 fbsd3 A 192.168.15.23 fbsd4 A 192.168.15.24 fbsd5 6 IN A 192.168.15.25 fbsd6 A 192.168.15.26 fbsd7 A 192.168.15.27 fbsd8 A 192.168.15.28 fbsd9 A 192.168.15.29 fbsd10 A 192.168.15.30 test-zla A 192.168.15.254 test-zla A 192.168.15.154 test-zla A 192.168.15.54 $INCLUDE /etc/bind/nt-lnet-aliases $INCLUDE /etc/bind/linux16 quit CNAME please.use.exit.to.quit.nslookup. linux16-254 A 192.168.16.254 linux15-254 A 192.168.15.254 home 1 IN A 85.202.152.56 linux200 A 192.168.15.200 linux201 A 192.168.15.201 linux202 A 192.168.15.202 linux203 A 192.168.15.203 linux204 A 192.168.15.204 linux205 A 192.168.15.205 linux206 A 192.168.15.206 linux207 A 192.168.15.207 linux208 A 192.168.15.208 linux209 A 192.168.15.209 linux210 A 192.168.15.210 linux211 A 192.168.15.211 linux212 A 192.168.15.212 linux213 A 192.168.15.213 linux214 A 192.168.15.214 linux215 A 192.168.15.215 linux216 A 192.168.15.216 linux217 A 192.168.15.217 linux218 A 192.168.15.218 linux219 A 192.168.15.219 linux220 A 192.168.15.220 linux221 A 192.168.15.221 linux222 A 192.168.15.222 linux223 A 192.168.15.223 linux224 A 192.168.15.224 linux225 A 192.168.15.225 linux226 A 192.168.15.226 linux227 A 192.168.15.227 linux228 A 192.168.15.228 linux229 A 192.168.15.229 linux230 A 192.168.15.230 linux231 A 192.168.15.231 linux232 A 192.168.15.232 linux233 A 192.168.15.233 linux234 A 192.168.15.234 linux235 A 192.168.15.235 linux236 A 192.168.15.236 linux237 A 192.168.15.237 linux238 A 192.168.15.238 linux239 A 192.168.15.239 linux240 A 192.168.15.240 linux241 A 192.168.15.241 linux242 A 192.168.15.242 linux243 A 192.168.15.243 linux244 A 192.168.15.244 linux245 A 192.168.15.245 linux246 A 192.168.15.246 linux247 A 192.168.15.247 linux248 A 192.168.15.248 linux249 A 192.168.15.249 linux250 A 192.168.15.250 linux251 A 192.168.15.251 linux252 A 192.168.15.252
$TTL 3000h @ SOA linux.nt. imchubin.nt.com.ua. 2004050801 ( 10h ; slave-server connection period 1h ; retry 1w ; lifetime 1h ) ; negative ttl NS @ A 10.0.35.1 herz A 10.0.35.1 lav NS server2.lav server2.lav A 192.168.15.21 yuriksat NS yuriksat.yuriksat yuriksat.yuriksat A 192.168.15.2 sergey NS yellow.sergey yellow.sergey A 192.168.15.4 debian NS debian.debian debian.debian A 192.168.15.3
@ SOA yellow.sergey.unix.nt. hostmaster.sergey.unix.nt. ( 2006092001 10h 1h 1w 3h) NS yellow.sergey.unix.nt. ; NS yellow --> То же самое! yellow A 192.168.15.4 blue A 192.168.15.99
options { directory "/var/cache/bind"; // If there is a firewall between you and nameservers you want // to talk to, you might need to uncomment the query-source // directive below. Previous versions of BIND always asked // questions using port 53, but BIND 8.1 and later use an unprivileged // port by default. // query-source address * port 53; // If your ISP provided one or more IP addresses for stable // nameservers, you probably want to use them as forwarders. // Uncomment the following block, and insert the addresses replacing // the all-0's placeholder. forwarders { 192.168.15.254; }; //Передавать запрос на 192.168.15.254 если не в силах его обработать сам! // Для использования зоны линукс.нт - в инете ее нет !! auth-nxdomain no; # conform to RFC1035 //Чьи запросы обрабатывать? allow-query { 127.0.0.1; 192.168.15.0/24; }; //Привязка к определенным интерфейсам listen-on { 192.168.15.2; 127.0.0.1; }; };
Время первой команды журнала | 16:27:20 2006- 9-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Время последней команды журнала | 17:40:09 2006- 9-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Количество командных строк в журнале | 98 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Процент команд с ненулевым кодом завершения, % | 8.16 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Процент синтаксически неверно набранных команд, % | 0.00 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Суммарное время работы с терминалом *, час | 1.21 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Количество командных строк в единицу времени, команда/мин | 1.35 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Частота использования команд |
|
В журнал автоматически попадают все команды, данные в любом терминале системы.
Для того чтобы убедиться, что журнал на текущем терминале ведётся, и команды записываются, дайте команду w. В поле WHAT, соответствующем текущему терминалу, должна быть указана программа script.
Команды, при наборе которых были допущены синтаксические ошибки, выводятся перечёркнутым текстом:
$ l s-l bash: l: command not found |
Если код завершения команды равен нулю, команда была выполнена без ошибок. Команды, код завершения которых отличен от нуля, выделяются цветом.
$ test 5 -lt 4 |
Команды, ход выполнения которых был прерван пользователем, выделяются цветом.
$ find / -name abc find: /home/devi-orig/.gnome2: Keine Berechtigung find: /home/devi-orig/.gnome2_private: Keine Berechtigung find: /home/devi-orig/.nautilus/metafiles: Keine Berechtigung find: /home/devi-orig/.metacity: Keine Berechtigung find: /home/devi-orig/.inkscape: Keine Berechtigung ^C |
Команды, выполненные с привилегиями суперпользователя, выделяются слева красной чертой.
# id uid=0(root) gid=0(root) Gruppen=0(root) |
Изменения, внесённые в текстовый файл с помощью редактора, запоминаются и показываются в журнале в формате ed. Строки, начинающиеся символом "<", удалены, а строки, начинающиеся символом ">" -- добавлены.
$ vi ~/.bashrc
|
Для того чтобы изменить файл в соответствии с показанными в диффшоте изменениями, можно воспользоваться командой patch. Нужно скопировать изменения, запустить программу patch, указав в качестве её аргумента файл, к которому применяются изменения, и всавить скопированный текст:
$ patch ~/.bashrc |
Для того чтобы получить краткую справочную информацию о команде, нужно подвести к ней мышь. Во всплывающей подсказке появится краткое описание команды.
Если справочная информация о команде есть, команда выделяется голубым фоном, например: vi. Если справочная информация отсутствует, команда выделяется розовым фоном, например: notepad.exe. Справочная информация может отсутствовать в том случае, если (1) команда введена неверно; (2) если распознавание команды LiLaLo выполнено неверно; (3) если информация о команде неизвестна LiLaLo. Последнее возможно для редких команд.
Большие, в особенности многострочные, всплывающие подсказки лучше всего показываются браузерами KDE Konqueror, Apple Safari и Microsoft Internet Explorer. В браузерах Mozilla и Firefox они отображаются не полностью, а вместо перевода строки выводится специальный символ.
Время ввода команды, показанное в журнале, соответствует времени начала ввода командной строки, которое равно тому моменту, когда на терминале появилось приглашение интерпретатора
Имя терминала, на котором была введена команда, показано в специальном блоке. Этот блок показывается только в том случае, если терминал текущей команды отличается от терминала предыдущей.
Вывод не интересующих вас в настоящий момент элементов журнала, таких как время, имя терминала и других, можно отключить. Для этого нужно воспользоваться формой управления журналом вверху страницы.
Небольшие комментарии к командам можно вставлять прямо из командной строки. Комментарий вводится прямо в командную строку, после символов #^ или #v. Символы ^ и v показывают направление выбора команды, к которой относится комментарий: ^ - к предыдущей, v - к следующей. Например, если в командной строке было введено:
$ whoami
user
$ #^ Интересно, кто я?в журнале это будет выглядеть так:
$ whoami
user
Интересно, кто я? |
Если комментарий содержит несколько строк, его можно вставить в журнал следующим образом:
$ whoami
user
$ cat > /dev/null #^ Интересно, кто я?
Программа whoami выводит имя пользователя, под которым мы зарегистрировались в системе. - Она не может ответить на вопрос о нашем назначении в этом мире.В журнале это будет выглядеть так:
$ whoami user
|
Комментарии, не относящиеся непосредственно ни к какой из команд, добавляются точно таким же способом, только вместо симолов #^ или #v нужно использовать символы #=
1 2 3 4Группы команд, выполненных на разных терминалах, разделяются специальной линией. Под этой линией в правом углу показано имя терминала, на котором выполнялись команды. Для того чтобы посмотреть команды только одного сенса, нужно щёкнуть по этому названию.
LiLaLo (L3) расшифровывается как Live Lab Log.
Программа разработана для повышения эффективности обучения Unix/Linux-системам.
(c) Игорь Чубин, 2004-2008