Журнал лабораторных работ

Содержание

Журнал

Вторник (12/13/11)

/dev/ttyp2
17:22:44
#ssh root@213.160.142.162 -p33
192.221.0.0,http          213.160.0.0               tcp        4533K      149K
95.142.0.0,http           213.160.0.0               tcp        4087K      78K
213.186.0.0,http          213.160.0.0               tcp        3746K      85K
208.65.0.0,http           213.160.0.0               tcp        3536K      122K
173.194.0.0,http          213.160.0.0               tcp        2898K      122
213.160.0.0               46.182.0.0,http           tcp        2690K      54K
64.34.0.0,https           213.160.0.0               tcp        2037K      71K
85.17.0.0,http            213.160.0.0               tcp        1239K      71K
213.160.0.0               87.240.0.0,http           tcp        914K       19K
199.48.0.0,https          213.160.0.0               tcp        835K       22K
93.114.0.0,https          213.160.0.0               tcp        696K       71K
173.254.0.0,https         213.160.0.0               tcp        621K       28K
206.33.0.0,http           213.160.0.0               tcp        607K       15K
77.47.0.0.dynamic.ca,http 213.160.0.0               tcp        579K       17K
qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
Segmentation fault
[root@idecogate root]# trafshow
imq0: arptype 65535 not supported by libpcap - falling back to cooked socket
imq1: arptype 65535 not supported by libpcap - falling back to cooked socket
17:22:44
#ssh root@213.160.142.162 -p33
[root@idecogate root]# trafshow
imq0: arptype 65535 not supported by libpcap - falling back to cooked socket
imq1: arptype 65535 not supported by libpcap - falling back to cooked socket
192.221.0.0,http          213.160.0.0               tcp        4533K      149K
95.142.0.0,http           213.160.0.0               tcp        4087K      78K
213.186.0.0,http          213.160.0.0               tcp        3746K      85K
208.65.0.0,http           213.160.0.0               tcp        3536K      122K
173.194.0.0,http          213.160.0.0               tcp        2898K      122
213.160.0.0               46.182.0.0,http           tcp        2690K      54K
64.34.0.0,https           213.160.0.0               tcp        2037K      71K
...
199.48.0.0,https          213.160.0.0               tcp        835K       22K
93.114.0.0,https          213.160.0.0               tcp        696K       71K
173.254.0.0,https         213.160.0.0               tcp        621K       28K
206.33.0.0,http           213.160.0.0               tcp        607K       15K
77.47.0.0.dynamic.ca,http 213.160.0.0               tcp        579K       17K
qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
Segmentation fault
[root@idecogate root]# trafshow
imq0: arptype 65535 not supported by libpcap - falling back to cooked socket
imq1: arptype 65535 not supported by libpcap - falling back to cooked socket
17:22:44
#ssh root@213.160.142.162 -p33
root@213.160.142.162's password:
[root@idecogate root]# ping 192.168.64.1
PING 192.168.64.1 (192.168.64.1) 56(84) bytes of data.
64 bytes from 192.168.64.1: icmp_seq=1 ttl=30 time=3.43 ms
64 bytes from 192.168.64.1: icmp_seq=2 ttl=30 time=2.13 ms
--- 192.168.64.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 2.134/2.783/3.433/0.651 ms
[root@idecogate root]# ping 192.168.84.1
PING 192.168.84.1 (192.168.84.1) 56(84) bytes of data.
...
199.48.0.0,https          213.160.0.0               tcp        835K       22K
93.114.0.0,https          213.160.0.0               tcp        696K       71K
173.254.0.0,https         213.160.0.0               tcp        621K       28K
206.33.0.0,http           213.160.0.0               tcp        607K       15K
77.47.0.0.dynamic.ca,http 213.160.0.0               tcp        579K       17K
qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
Segmentation fault
[root@idecogate root]# trafshow
imq0: arptype 65535 not supported by libpcap - falling back to cooked socket
imq1: arptype 65535 not supported by libpcap - falling back to cooked socket
17:22:44
#ssh root@213.160.142.162 -p33
192.221.0.0,http          213.160.0.0               tcp        4533K      149K
95.142.0.0,http           213.160.0.0               tcp        4087K      78K
213.186.0.0,http          213.160.0.0               tcp        3746K      85K
208.65.0.0,http           213.160.0.0               tcp        3536K      122K
173.194.0.0,http          213.160.0.0               tcp        2898K      122
213.160.0.0               46.182.0.0,http           tcp        2690K      54K
64.34.0.0,https           213.160.0.0               tcp        2037K      71K
85.17.0.0,http            213.160.0.0               tcp        1239K      71K
213.160.0.0               87.240.0.0,http           tcp        914K       19K
199.48.0.0,https          213.160.0.0               tcp        835K       22K
93.114.0.0,https          213.160.0.0               tcp        696K       71K
173.254.0.0,https         213.160.0.0               tcp        621K       28K
206.33.0.0,http           213.160.0.0               tcp        607K       15K
77.47.0.0.dynamic.ca,http 213.160.0.0               tcp        579K       17K
qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
Segmentation fault
[root@idecogate root]# trafshow
imq0: arptype 65535 not supported by libpcap - falling back to cooked socket
imq1: arptype 65535 not supported by libpcap - falling back to cooked socket
17:22:44
#ssh root@213.160.142.162 -p33
192.221.0.0,http          213.160.0.0               tcp        4533K      149K
95.142.0.0,http           213.160.0.0               tcp        4087K      78K
213.186.0.0,http          213.160.0.0               tcp        3746K      85K
208.65.0.0,http           213.160.0.0               tcp        3536K      122K
173.194.0.0,http          213.160.0.0               tcp        2898K      122
213.160.0.0               46.182.0.0,http           tcp        2690K      54K
64.34.0.0,https           213.160.0.0               tcp        2037K      71K
85.17.0.0,http            213.160.0.0               tcp        1239K      71K
213.160.0.0               87.240.0.0,http           tcp        914K       19K
199.48.0.0,https          213.160.0.0               tcp        835K       22K
93.114.0.0,https          213.160.0.0               tcp        696K       71K
173.254.0.0,https         213.160.0.0               tcp        621K       28K
206.33.0.0,http           213.160.0.0               tcp        607K       15K
77.47.0.0.dynamic.ca,http 213.160.0.0               tcp        579K       17K
qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
Segmentation fault
[root@idecogate root]# trafshow
imq0: arptype 65535 not supported by libpcap - falling back to cooked socket
imq1: arptype 65535 not supported by libpcap - falling back to cooked socket
17:22:44
#ssh root@213.160.142.162 -p33
192.221.0.0,http          213.160.0.0               tcp        4533K      149K
95.142.0.0,http           213.160.0.0               tcp        4087K      78K
213.186.0.0,http          213.160.0.0               tcp        3746K      85K
208.65.0.0,http           213.160.0.0               tcp        3536K      122K
173.194.0.0,http          213.160.0.0               tcp        2898K      122
213.160.0.0               46.182.0.0,http           tcp        2690K      54K
64.34.0.0,https           213.160.0.0               tcp        2037K      71K
85.17.0.0,http            213.160.0.0               tcp        1239K      71K
213.160.0.0               87.240.0.0,http           tcp        914K       19K
199.48.0.0,https          213.160.0.0               tcp        835K       22K
93.114.0.0,https          213.160.0.0               tcp        696K       71K
173.254.0.0,https         213.160.0.0               tcp        621K       28K
206.33.0.0,http           213.160.0.0               tcp        607K       15K
77.47.0.0.dynamic.ca,http 213.160.0.0               tcp        579K       17K
qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
Segmentation fault
[root@idecogate root]# trafshow
imq0: arptype 65535 not supported by libpcap - falling back to cooked socket
imq1: arptype 65535 not supported by libpcap - falling back to cooked socket
17:22:44
#ssh root@213.160.142.162 -p33
192.221.0.0,http          213.160.0.0               tcp        4533K      149K
95.142.0.0,http           213.160.0.0               tcp        4087K      78K
213.186.0.0,http          213.160.0.0               tcp        3746K      85K
208.65.0.0,http           213.160.0.0               tcp        3536K      122K
173.194.0.0,http          213.160.0.0               tcp        2898K      122
213.160.0.0               46.182.0.0,http           tcp        2690K      54K
64.34.0.0,https           213.160.0.0               tcp        2037K      71K
85.17.0.0,http            213.160.0.0               tcp        1239K      71K
213.160.0.0               87.240.0.0,http           tcp        914K       19K
199.48.0.0,https          213.160.0.0               tcp        835K       22K
93.114.0.0,https          213.160.0.0               tcp        696K       71K
173.254.0.0,https         213.160.0.0               tcp        621K       28K
206.33.0.0,http           213.160.0.0               tcp        607K       15K
77.47.0.0.dynamic.ca,http 213.160.0.0               tcp        579K       17K
qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
Segmentation fault
[root@idecogate root]# trafshow
imq0: arptype 65535 not supported by libpcap - falling back to cooked socket
imq1: arptype 65535 not supported by libpcap - falling back to cooked socket
17:22:44
#ssh root@213.160.142.162 -p33
192.221.0.0,http          213.160.0.0               tcp        4533K      149K
95.142.0.0,http           213.160.0.0               tcp        4087K      78K
213.186.0.0,http          213.160.0.0               tcp        3746K      85K
208.65.0.0,http           213.160.0.0               tcp        3536K      122K
173.194.0.0,http          213.160.0.0               tcp        2898K      122
213.160.0.0               46.182.0.0,http           tcp        2690K      54K
64.34.0.0,https           213.160.0.0               tcp        2037K      71K
85.17.0.0,http            213.160.0.0               tcp        1239K      71K
213.160.0.0               87.240.0.0,http           tcp        914K       19K
199.48.0.0,https          213.160.0.0               tcp        835K       22K
93.114.0.0,https          213.160.0.0               tcp        696K       71K
173.254.0.0,https         213.160.0.0               tcp        621K       28K
206.33.0.0,http           213.160.0.0               tcp        607K       15K
77.47.0.0.dynamic.ca,http 213.160.0.0               tcp        579K       17K
qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
Segmentation fault
[root@idecogate root]# trafshow
imq0: arptype 65535 not supported by libpcap - falling back to cooked socket
imq1: arptype 65535 not supported by libpcap - falling back to cooked socket
17:22:44
#ssh root@213.160.142.162 -p33
192.221.0.0,http          213.160.0.0               tcp        4533K      149K
95.142.0.0,http           213.160.0.0               tcp        4087K      78K
213.186.0.0,http          213.160.0.0               tcp        3746K      85K
208.65.0.0,http           213.160.0.0               tcp        3536K      122K
173.194.0.0,http          213.160.0.0               tcp        2898K      122
213.160.0.0               46.182.0.0,http           tcp        2690K      54K
64.34.0.0,https           213.160.0.0               tcp        2037K      71K
85.17.0.0,http            213.160.0.0               tcp        1239K      71K
213.160.0.0               87.240.0.0,http           tcp        914K       19K
199.48.0.0,https          213.160.0.0               tcp        835K       22K
93.114.0.0,https          213.160.0.0               tcp        696K       71K
173.254.0.0,https         213.160.0.0               tcp        621K       28K
206.33.0.0,http           213.160.0.0               tcp        607K       15K
77.47.0.0.dynamic.ca,http 213.160.0.0               tcp        579K       17K
qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
Segmentation fault
[root@idecogate root]# trafshow
imq0: arptype 65535 not supported by libpcap - falling back to cooked socket
imq1: arptype 65535 not supported by libpcap - falling back to cooked socket
17:22:44
#ssh root@213.160.142.162 -p33
[root@idecogate root]# trafshow
imq0: arptype 65535 not supported by libpcap - falling back to cooked socket
imq1: arptype 65535 not supported by libpcap - falling back to cooked socket
192.221.0.0,http          213.160.0.0               tcp        4533K      149K
95.142.0.0,http           213.160.0.0               tcp        4087K      78K
213.186.0.0,http          213.160.0.0               tcp        3746K      85K
208.65.0.0,http           213.160.0.0               tcp        3536K      122K
173.194.0.0,http          213.160.0.0               tcp        2898K      122
213.160.0.0               46.182.0.0,http           tcp        2690K      54K
64.34.0.0,https           213.160.0.0               tcp        2037K      71K
...
199.48.0.0,https          213.160.0.0               tcp        835K       22K
93.114.0.0,https          213.160.0.0               tcp        696K       71K
173.254.0.0,https         213.160.0.0               tcp        621K       28K
206.33.0.0,http           213.160.0.0               tcp        607K       15K
77.47.0.0.dynamic.ca,http 213.160.0.0               tcp        579K       17K
qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
Segmentation fault
[root@idecogate root]# trafshow
imq0: arptype 65535 not supported by libpcap - falling back to cooked socket
imq1: arptype 65535 not supported by libpcap - falling back to cooked socket
17:22:44
#ssh root@213.160.142.162 -p33
root@213.160.142.162's password:
[root@idecogate root]# ping 192.168.64.1
PING 192.168.64.1 (192.168.64.1) 56(84) bytes of data.
64 bytes from 192.168.64.1: icmp_seq=1 ttl=30 time=3.43 ms
64 bytes from 192.168.64.1: icmp_seq=2 ttl=30 time=2.13 ms
--- 192.168.64.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 2.134/2.783/3.433/0.651 ms
[root@idecogate root]# ping 192.168.84.1
PING 192.168.84.1 (192.168.84.1) 56(84) bytes of data.
...
199.48.0.0,https          213.160.0.0               tcp        835K       22K
93.114.0.0,https          213.160.0.0               tcp        696K       71K
173.254.0.0,https         213.160.0.0               tcp        621K       28K
206.33.0.0,http           213.160.0.0               tcp        607K       15K
77.47.0.0.dynamic.ca,http 213.160.0.0               tcp        579K       17K
qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
Segmentation fault
[root@idecogate root]# trafshow
imq0: arptype 65535 not supported by libpcap - falling back to cooked socket
imq1: arptype 65535 not supported by libpcap - falling back to cooked socket
17:28:06
#^C

17:28:06
#^C

17:28:06
#^C

17:28:06
#^C

17:28:06
#^C

17:28:06
#^C

17:28:06
#^C

17:28:06
#^C

17:28:06
#^C

17:28:06
#^C

17:28:06
#^C

17:28:06
#^C

17:28:06
#^C

17:28:06
#^C

17:28:06
#^C

17:28:06
#^C

/dev/ttyp0
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:37:42
#nmap 192.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:38 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:39:01
#nmap -Pn 168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:39 EET
17:40:01
#nmap -v .168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:40 EET
Initiating Ping Scan at 18:40
Scanning 192.168.30.190 [4 ports]
Completed Ping Scan at 18:40, 3.04s elapsed (1 total hosts)
Nmap scan report for 192.168.30.190 [host down]
Read data files from: /usr/local/share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.12 seconds
           Raw packets sent: 8 (304B) | Rcvd: 0 (0B)
17:40:01
#nmap -v .168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:40 EET
Initiating Ping Scan at 18:40
Scanning 192.168.30.190 [4 ports]
Completed Ping Scan at 18:40, 3.04s elapsed (1 total hosts)
Nmap scan report for 192.168.30.190 [host down]
Read data files from: /usr/local/share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.12 seconds
           Raw packets sent: 8 (304B) | Rcvd: 0 (0B)
17:40:01
#nmap -v .168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:40 EET
Initiating Ping Scan at 18:40
Scanning 192.168.30.190 [4 ports]
Completed Ping Scan at 18:40, 3.04s elapsed (1 total hosts)
Nmap scan report for 192.168.30.190 [host down]
Read data files from: /usr/local/share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.12 seconds
           Raw packets sent: 8 (304B) | Rcvd: 0 (0B)
17:40:01
#nmap -v .168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:40 EET
Initiating Ping Scan at 18:40
Scanning 192.168.30.190 [4 ports]
Completed Ping Scan at 18:40, 3.04s elapsed (1 total hosts)
Nmap scan report for 192.168.30.190 [host down]
Read data files from: /usr/local/share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.12 seconds
           Raw packets sent: 8 (304B) | Rcvd: 0 (0B)
17:40:01
#nmap -v .168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:40 EET
Initiating Ping Scan at 18:40
Scanning 192.168.30.190 [4 ports]
Completed Ping Scan at 18:40, 3.04s elapsed (1 total hosts)
Nmap scan report for 192.168.30.190 [host down]
Read data files from: /usr/local/share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.12 seconds
           Raw packets sent: 8 (304B) | Rcvd: 0 (0B)
17:40:01
#nmap -v .168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:40 EET
Initiating Ping Scan at 18:40
Scanning 192.168.30.190 [4 ports]
Completed Ping Scan at 18:40, 3.04s elapsed (1 total hosts)
Nmap scan report for 192.168.30.190 [host down]
Read data files from: /usr/local/share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.12 seconds
           Raw packets sent: 8 (304B) | Rcvd: 0 (0B)
17:40:01
#nmap -v .168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:40 EET
Initiating Ping Scan at 18:40
Scanning 192.168.30.190 [4 ports]
Completed Ping Scan at 18:40, 3.04s elapsed (1 total hosts)
Nmap scan report for 192.168.30.190 [host down]
Read data files from: /usr/local/share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.12 seconds
           Raw packets sent: 8 (304B) | Rcvd: 0 (0B)
17:40:01
#nmap -v .168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:40 EET
Initiating Ping Scan at 18:40
Scanning 192.168.30.190 [4 ports]
Completed Ping Scan at 18:40, 3.04s elapsed (1 total hosts)
Nmap scan report for 192.168.30.190 [host down]
Read data files from: /usr/local/share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.12 seconds
           Raw packets sent: 8 (304B) | Rcvd: 0 (0B)
17:40:01
#nmap -v .168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:40 EET
Initiating Ping Scan at 18:40
Scanning 192.168.30.190 [4 ports]
Completed Ping Scan at 18:40, 3.04s elapsed (1 total hosts)
Nmap scan report for 192.168.30.190 [host down]
Read data files from: /usr/local/share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.12 seconds
           Raw packets sent: 8 (304B) | Rcvd: 0 (0B)
17:40:01
#nmap -v .168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:40 EET
Initiating Ping Scan at 18:40
Scanning 192.168.30.190 [4 ports]
Completed Ping Scan at 18:40, 3.04s elapsed (1 total hosts)
Nmap scan report for 192.168.30.190 [host down]
Read data files from: /usr/local/share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.12 seconds
           Raw packets sent: 8 (304B) | Rcvd: 0 (0B)
17:40:01
#nmap -v .168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:40 EET
Initiating Ping Scan at 18:40
Scanning 192.168.30.190 [4 ports]
Completed Ping Scan at 18:40, 3.04s elapsed (1 total hosts)
Nmap scan report for 192.168.30.190 [host down]
Read data files from: /usr/local/share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.12 seconds
           Raw packets sent: 8 (304B) | Rcvd: 0 (0B)
17:40:01
#nmap -v .168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:40 EET
Initiating Ping Scan at 18:40
Scanning 192.168.30.190 [4 ports]
Completed Ping Scan at 18:40, 3.04s elapsed (1 total hosts)
Nmap scan report for 192.168.30.190 [host down]
Read data files from: /usr/local/share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.12 seconds
           Raw packets sent: 8 (304B) | Rcvd: 0 (0B)
17:40:01
#nmap -v .168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:40 EET
Initiating Ping Scan at 18:40
Scanning 192.168.30.190 [4 ports]
Completed Ping Scan at 18:40, 3.04s elapsed (1 total hosts)
Nmap scan report for 192.168.30.190 [host down]
Read data files from: /usr/local/share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.12 seconds
           Raw packets sent: 8 (304B) | Rcvd: 0 (0B)
17:40:01
#nmap -v .168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:40 EET
Initiating Ping Scan at 18:40
Scanning 192.168.30.190 [4 ports]
Completed Ping Scan at 18:40, 3.04s elapsed (1 total hosts)
Nmap scan report for 192.168.30.190 [host down]
Read data files from: /usr/local/share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.12 seconds
           Raw packets sent: 8 (304B) | Rcvd: 0 (0B)
17:40:21
#ping 192.168.30.190
PING 192.168.30.190 (192.168.30.190): 56 data bytes
64 bytes from 192.168.30.190: icmp_seq=0 ttl=64 time=1.875 ms
64 bytes from 192.168.30.190: icmp_seq=1 ttl=64 time=4.945 ms
^C
--- 192.168.30.190 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.875/3.410/4.945/1.535 ms
17:40:21
#ping 192.168.30.190
PING 192.168.30.190 (192.168.30.190): 56 data bytes
64 bytes from 192.168.30.190: icmp_seq=0 ttl=64 time=1.875 ms
64 bytes from 192.168.30.190: icmp_seq=1 ttl=64 time=4.945 ms
^C
--- 192.168.30.190 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.875/3.410/4.945/1.535 ms
17:40:21
#ping 192.168.30.190
PING 192.168.30.190 (192.168.30.190): 56 data bytes
64 bytes from 192.168.30.190: icmp_seq=0 ttl=64 time=1.875 ms
64 bytes from 192.168.30.190: icmp_seq=1 ttl=64 time=4.945 ms
^C
--- 192.168.30.190 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.875/3.410/4.945/1.535 ms
17:40:21
#ping 192.168.30.190
PING 192.168.30.190 (192.168.30.190): 56 data bytes
64 bytes from 192.168.30.190: icmp_seq=0 ttl=64 time=1.875 ms
64 bytes from 192.168.30.190: icmp_seq=1 ttl=64 time=4.945 ms
^C
--- 192.168.30.190 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.875/3.410/4.945/1.535 ms
17:40:21
#ping 192.168.30.190
PING 192.168.30.190 (192.168.30.190): 56 data bytes
64 bytes from 192.168.30.190: icmp_seq=0 ttl=64 time=1.875 ms
64 bytes from 192.168.30.190: icmp_seq=1 ttl=64 time=4.945 ms
^C
--- 192.168.30.190 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.875/3.410/4.945/1.535 ms
17:40:21
#ping 192.168.30.190
PING 192.168.30.190 (192.168.30.190): 56 data bytes
64 bytes from 192.168.30.190: icmp_seq=0 ttl=64 time=1.875 ms
64 bytes from 192.168.30.190: icmp_seq=1 ttl=64 time=4.945 ms
^C
--- 192.168.30.190 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.875/3.410/4.945/1.535 ms
17:40:39
#ping -A .168.30.190
PING 192.168.30.190 (192.168.30.190): 56 data bytes
64 bytes from 192.168.30.190: icmp_seq=0 ttl=64 time=1.838 ms
64 bytes from 192.168.30.190: icmp_seq=1 ttl=64 time=1.807 ms
64 bytes from 192.168.30.190: icmp_seq=2 ttl=64 time=1.125 ms
^C
--- 192.168.30.190 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.125/1.590/1.838/0.329 ms
17:40:39
#ping -A .168.30.190
PING 192.168.30.190 (192.168.30.190): 56 data bytes
64 bytes from 192.168.30.190: icmp_seq=0 ttl=64 time=1.838 ms
64 bytes from 192.168.30.190: icmp_seq=1 ttl=64 time=1.807 ms
64 bytes from 192.168.30.190: icmp_seq=2 ttl=64 time=1.125 ms
^C
--- 192.168.30.190 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.125/1.590/1.838/0.329 ms
17:40:39
#ping -A .168.30.190
PING 192.168.30.190 (192.168.30.190): 56 data bytes
64 bytes from 192.168.30.190: icmp_seq=0 ttl=64 time=1.838 ms
64 bytes from 192.168.30.190: icmp_seq=1 ttl=64 time=1.807 ms
64 bytes from 192.168.30.190: icmp_seq=2 ttl=64 time=1.125 ms
^C
--- 192.168.30.190 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.125/1.590/1.838/0.329 ms
17:40:39
#ping -A .168.30.190
PING 192.168.30.190 (192.168.30.190): 56 data bytes
64 bytes from 192.168.30.190: icmp_seq=0 ttl=64 time=1.838 ms
64 bytes from 192.168.30.190: icmp_seq=1 ttl=64 time=1.807 ms
64 bytes from 192.168.30.190: icmp_seq=2 ttl=64 time=1.125 ms
^C
--- 192.168.30.190 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.125/1.590/1.838/0.329 ms
17:40:39
#ping -A .168.30.190
PING 192.168.30.190 (192.168.30.190): 56 data bytes
64 bytes from 192.168.30.190: icmp_seq=0 ttl=64 time=1.838 ms
64 bytes from 192.168.30.190: icmp_seq=1 ttl=64 time=1.807 ms
64 bytes from 192.168.30.190: icmp_seq=2 ttl=64 time=1.125 ms
^C
--- 192.168.30.190 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.125/1.590/1.838/0.329 ms
17:40:39
#ping -A .168.30.190
PING 192.168.30.190 (192.168.30.190): 56 data bytes
64 bytes from 192.168.30.190: icmp_seq=0 ttl=64 time=1.838 ms
64 bytes from 192.168.30.190: icmp_seq=1 ttl=64 time=1.807 ms
64 bytes from 192.168.30.190: icmp_seq=2 ttl=64 time=1.125 ms
^C
--- 192.168.30.190 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.125/1.590/1.838/0.329 ms
17:41:02
#nmap -A92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.41 seconds
17:41:02
#nmap -A92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.41 seconds
17:41:02
#nmap -A92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.41 seconds
17:41:02
#nmap -A92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.41 seconds
17:41:02
#nmap -A92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.41 seconds
17:41:02
#nmap -A92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.41 seconds
17:41:02
#nmap -A92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.41 seconds
17:41:02
#nmap -A92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.41 seconds
17:41:02
#nmap -A92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.41 seconds
17:41:02
#nmap -A92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.41 seconds
17:41:02
#nmap -A92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.41 seconds
17:41:02
#nmap -A92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.41 seconds
17:41:02
#nmap -A92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.41 seconds
17:41:02
#nmap -A92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.41 seconds
17:41:13
#nmap -PS92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 2.11 seconds
17:41:13
#nmap -PS92.168.30.190
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-13 18:41 EET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 2.11 seconds

Статистика

Время первой команды журнала17:22:44 2011-12-13
Время последней команды журнала17:41:13 2011-12-13
Количество командных строк в журнале101
Процент команд с ненулевым кодом завершения, % 0.00
Процент синтаксически неверно набранных команд, % 0.00
Суммарное время работы с терминалом *, час 0.31
Количество командных строк в единицу времени, команда/мин 5.46
Частота использования команд
nmap62|=============================================================| 61.39%
^C16|===============| 15.84%
ping12|===========| 11.88%
ssh11|==========| 10.89%
____
*) Интервалы неактивности длительностью 30 минут и более не учитываются

Справка

Для того чтобы использовать LiLaLo, не нужно знать ничего особенного: всё происходит само собой. Однако, чтобы ведение и последующее использование журналов было как можно более эффективным, желательно иметь в виду следующее:
  1. В журнал автоматически попадают все команды, данные в любом терминале системы.

  2. Для того чтобы убедиться, что журнал на текущем терминале ведётся, и команды записываются, дайте команду w. В поле WHAT, соответствующем текущему терминалу, должна быть указана программа script.

  3. Команды, при наборе которых были допущены синтаксические ошибки, выводятся перечёркнутым текстом:
    $ l s-l
    bash: l: command not found
    

  4. Если код завершения команды равен нулю, команда была выполнена без ошибок. Команды, код завершения которых отличен от нуля, выделяются цветом.
    $ test 5 -lt 4
    Обратите внимание на то, что код завершения команды может быть отличен от нуля не только в тех случаях, когда команда была выполнена с ошибкой. Многие команды используют код завершения, например, для того чтобы показать результаты проверки

  5. Команды, ход выполнения которых был прерван пользователем, выделяются цветом.
    $ 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
    

  6. Команды, выполненные с привилегиями суперпользователя, выделяются слева красной чертой.
    # id
    uid=0(root) gid=0(root) Gruppen=0(root)
    

  7. Изменения, внесённые в текстовый файл с помощью редактора, запоминаются и показываются в журнале в формате ed. Строки, начинающиеся символом "<", удалены, а строки, начинающиеся символом ">" -- добавлены.
    $ vi ~/.bashrc
    2a3,5
    >    if [ -f /usr/local/etc/bash_completion ]; then
    >         . /usr/local/etc/bash_completion
    >        fi
    

  8. Для того чтобы изменить файл в соответствии с показанными в диффшоте изменениями, можно воспользоваться командой patch. Нужно скопировать изменения, запустить программу patch, указав в качестве её аргумента файл, к которому применяются изменения, и всавить скопированный текст:
    $ patch ~/.bashrc
    В данном случае изменения применяются к файлу ~/.bashrc

  9. Для того чтобы получить краткую справочную информацию о команде, нужно подвести к ней мышь. Во всплывающей подсказке появится краткое описание команды.

    Если справочная информация о команде есть, команда выделяется голубым фоном, например: vi. Если справочная информация отсутствует, команда выделяется розовым фоном, например: notepad.exe. Справочная информация может отсутствовать в том случае, если (1) команда введена неверно; (2) если распознавание команды LiLaLo выполнено неверно; (3) если информация о команде неизвестна LiLaLo. Последнее возможно для редких команд.

  10. Большие, в особенности многострочные, всплывающие подсказки лучше всего показываются браузерами KDE Konqueror, Apple Safari и Microsoft Internet Explorer. В браузерах Mozilla и Firefox они отображаются не полностью, а вместо перевода строки выводится специальный символ.

  11. Время ввода команды, показанное в журнале, соответствует времени начала ввода командной строки, которое равно тому моменту, когда на терминале появилось приглашение интерпретатора

  12. Имя терминала, на котором была введена команда, показано в специальном блоке. Этот блок показывается только в том случае, если терминал текущей команды отличается от терминала предыдущей.

  13. Вывод не интересующих вас в настоящий момент элементов журнала, таких как время, имя терминала и других, можно отключить. Для этого нужно воспользоваться формой управления журналом вверху страницы.

  14. Небольшие комментарии к командам можно вставлять прямо из командной строки. Комментарий вводится прямо в командную строку, после символов #^ или #v. Символы ^ и v показывают направление выбора команды, к которой относится комментарий: ^ - к предыдущей, v - к следующей. Например, если в командной строке было введено:

    $ whoami
    
    user
    
    $ #^ Интересно, кто я?
    
    в журнале это будет выглядеть так:
    $ whoami
    
    user
    
    Интересно, кто я?

  15. Если комментарий содержит несколько строк, его можно вставить в журнал следующим образом:

    $ whoami
    
    user
    
    $ cat > /dev/null #^ Интересно, кто я?
    
    Программа whoami выводит имя пользователя, под которым 
    мы зарегистрировались в системе.
    -
    Она не может ответить на вопрос о нашем назначении 
    в этом мире.
    
    В журнале это будет выглядеть так:
    $ whoami
    user
    
    Интересно, кто я?
    Программа whoami выводит имя пользователя, под которым
    мы зарегистрировались в системе.

    Она не может ответить на вопрос о нашем назначении
    в этом мире.
    Для разделения нескольких абзацев между собой используйте символ "-", один в строке.

  16. Комментарии, не относящиеся непосредственно ни к какой из команд, добавляются точно таким же способом, только вместо симолов #^ или #v нужно использовать символы #=

  17. Содержимое файла может быть показано в журнале. Для этого его нужно вывести с помощью программы cat. Если вывод команды отметить симоволами #!, содержимое файла будет показано в журнале в специально отведённой для этого секции.
  18. Для того чтобы вставить скриншот интересующего вас окна в журнал, нужно воспользоваться командой l3shot. После того как команда вызвана, нужно с помощью мыши выбрать окно, которое должно быть в журнале.
  19. Команды в журнале расположены в хронологическом порядке. Если две команды давались одна за другой, но на разных терминалах, в журнале они будут рядом, даже если они не имеют друг к другу никакого отношения.
    1
        2
    3   
        4
    
    Группы команд, выполненных на разных терминалах, разделяются специальной линией. Под этой линией в правом углу показано имя терминала, на котором выполнялись команды. Для того чтобы посмотреть команды только одного сенса, нужно щёкнуть по этому названию.

О программе

LiLaLo (L3) расшифровывается как Live Lab Log.
Программа разработана для повышения эффективности обучения Unix/Linux-системам.
(c) Игорь Чубин, 2004-2008

$Id$