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

Содержание

Журнал

Понедельник (11/27/06)

/dev/ttyv0
19:45:17
#ping 192.168.15.254
PING 192.168.15.254 (192.168.15.254): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
^C
--- 192.168.15.254 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
19:45:20
#ping 192.168.15.255
PING 192.168.15.255 (192.168.15.255): 56 data bytes
^C
--- 192.168.15.255 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
19:45:20
#ping 192.168.15.255
PING 192.168.15.255 (192.168.15.255): 56 data bytes
^C
--- 192.168.15.255 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
19:45:20
#ping 192.168.15.255
PING 192.168.15.255 (192.168.15.255): 56 data bytes
^C
--- 192.168.15.255 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
19:45:20
#ping 192.168.15.255
PING 192.168.15.255 (192.168.15.255): 56 data bytes
^C
--- 192.168.15.255 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
19:45:25
#ping 192.168.15.254
PING 192.168.15.254 (192.168.15.254): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
^C
--- 192.168.15.254 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
19:45:25
#ping 192.168.15.254
PING 192.168.15.254 (192.168.15.254): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
^C
--- 192.168.15.254 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
19:45:25
#ping 192.168.15.254
PING 192.168.15.254 (192.168.15.254): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
^C
--- 192.168.15.254 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
19:45:25
#ping 192.168.15.254
PING 192.168.15.254 (192.168.15.254): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
^C
--- 192.168.15.254 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
19:45:28
#ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=b<RXCSUM,TXCSUM,VLAN_MTU>
        inet6 fe80::213:d4ff:feb2:4fec%em0 prefixlen 64 scopeid 0x1
        inet 192.168.15.26 netmask 0xffffff00 broadcast 192.168.15.255
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
xl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        options=9<RXCSUM,VLAN_MTU>
        ether 00:04:79:67:96:71
...
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        vlan: 4 parent interface: em0
vlan5: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::213:d4ff:feb2:4fec%vlan5 prefixlen 64 scopeid 0x6
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        vlan: 5 parent interface: em0
19:45:28
#ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=b<RXCSUM,TXCSUM,VLAN_MTU>
        inet6 fe80::213:d4ff:feb2:4fec%em0 prefixlen 64 scopeid 0x1
        inet 192.168.15.26 netmask 0xffffff00 broadcast 192.168.15.255
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
xl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        options=9<RXCSUM,VLAN_MTU>
        ether 00:04:79:67:96:71
...
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        vlan: 4 parent interface: em0
vlan5: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::213:d4ff:feb2:4fec%vlan5 prefixlen 64 scopeid 0x6
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        vlan: 5 parent interface: em0
19:45:28
#ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=b<RXCSUM,TXCSUM,VLAN_MTU>
        inet6 fe80::213:d4ff:feb2:4fec%em0 prefixlen 64 scopeid 0x1
        inet 192.168.15.26 netmask 0xffffff00 broadcast 192.168.15.255
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
xl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        options=9<RXCSUM,VLAN_MTU>
        ether 00:04:79:67:96:71
...
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        vlan: 4 parent interface: em0
vlan5: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::213:d4ff:feb2:4fec%vlan5 prefixlen 64 scopeid 0x6
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        vlan: 5 parent interface: em0
19:45:28
#ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=b<RXCSUM,TXCSUM,VLAN_MTU>
        inet6 fe80::213:d4ff:feb2:4fec%em0 prefixlen 64 scopeid 0x1
        inet 192.168.15.26 netmask 0xffffff00 broadcast 192.168.15.255
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
xl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        options=9<RXCSUM,VLAN_MTU>
        ether 00:04:79:67:96:71
...
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        vlan: 4 parent interface: em0
vlan5: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::213:d4ff:feb2:4fec%vlan5 prefixlen 64 scopeid 0x6
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        vlan: 5 parent interface: em0
19:46:07
#[root@fbsd6:~]# ping 192.168.15.255
PING 192.168.15.255 (192.168.15.255): 56 data bytes
^C
--- 192.168.15.255 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
19:46:07
#[root@fbsd6:~]# ping 192.168.15.255
PING 192.168.15.255 (192.168.15.255): 56 data bytes
^C
--- 192.168.15.255 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
19:46:07
#[root@fbsd6:~]# ping 192.168.15.255
PING 192.168.15.255 (192.168.15.255): 56 data bytes
^C
--- 192.168.15.255 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
19:46:07
#[root@fbsd6:~]# ping 192.168.15.255
PING 192.168.15.255 (192.168.15.255): 56 data bytes
^C
--- 192.168.15.255 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
19:46:16
#ping 192.168.15.254
PING 192.168.15.254 (192.168.15.254): 56 data bytes
64 bytes from 192.168.15.254: icmp_seq=0 ttl=64 time=0.836 ms
64 bytes from 192.168.15.254: icmp_seq=1 ttl=64 time=0.626 ms
64 bytes from 192.168.15.254: icmp_seq=2 ttl=64 time=0.535 ms
^C
--- 192.168.15.254 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.535/0.666/0.836/0.126 ms
19:46:16
#ping 192.168.15.254
PING 192.168.15.254 (192.168.15.254): 56 data bytes
64 bytes from 192.168.15.254: icmp_seq=0 ttl=64 time=0.836 ms
64 bytes from 192.168.15.254: icmp_seq=1 ttl=64 time=0.626 ms
64 bytes from 192.168.15.254: icmp_seq=2 ttl=64 time=0.535 ms
^C
--- 192.168.15.254 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.535/0.666/0.836/0.126 ms
19:46:16
#ping 192.168.15.254
PING 192.168.15.254 (192.168.15.254): 56 data bytes
64 bytes from 192.168.15.254: icmp_seq=0 ttl=64 time=0.836 ms
64 bytes from 192.168.15.254: icmp_seq=1 ttl=64 time=0.626 ms
64 bytes from 192.168.15.254: icmp_seq=2 ttl=64 time=0.535 ms
^C
--- 192.168.15.254 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.535/0.666/0.836/0.126 ms
19:46:16
#ping 192.168.15.254
PING 192.168.15.254 (192.168.15.254): 56 data bytes
64 bytes from 192.168.15.254: icmp_seq=0 ttl=64 time=0.836 ms
64 bytes from 192.168.15.254: icmp_seq=1 ttl=64 time=0.626 ms
64 bytes from 192.168.15.254: icmp_seq=2 ttl=64 time=0.535 ms
^C
--- 192.168.15.254 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.535/0.666/0.836/0.126 ms
прошло 16 минут
/dev/ttyv0
20:02:26
#shutdown -p now
Shutdown NOW!
shutdown: [pid 3351]
20:02:26
#shutdown -p now
System shutdown time has arrived
Shutdown NOW!
shutdown: [pid 3351]
20:02:26
#shutdown -p now
System shutdown time has arrived
Shutdown NOW!
shutdown: [pid 3351]
20:02:26
#shutdown -p now
System shutdown time has arrived
Shutdown NOW!
shutdown: [pid 3351]

Вторник (11/28/06)

/dev/ttyv1
11:52:03
#vi /etc/motd
5,23d4
< Before seeking technical support, please use the following resources:
< 
< o  Security advisories and updated errata information for all releases are
<    at http://www.FreeBSD.org/releases/ - always consult the ERRATA section
<    for your release first as it's updated frequently.
< 
< o  The Handbook and FAQ documents are at http://www.FreeBSD.org/ and,
<    along with the mailing lists, can be searched by going to
<    http://www.FreeBSD.org/search/.  If the doc distribution has
<    been installed, they're also available formatted in /usr/share/doc.
< 
< If you still have a question or problem, please take the output of
< `uname -a', along with any relevant error messages, and email it
< as a question to the questions@FreeBSD.org mailing list.  If you are
< unfamiliar with FreeBSD's directory layout, please refer to the hier(7)
< manual page.  If you are not familiar with manual pages, type `man man'.
< 
< You may also use sysinstall(8) to re-enter the installation and
< configuration utility.  Edit /etc/motd to change this login announcement.
11:52:03
#vi /etc/motd
5,23d4
< Before seeking technical support, please use the following resources:
< 
< o  Security advisories and updated errata information for all releases are
<    at http://www.FreeBSD.org/releases/ - always consult the ERRATA section
<    for your release first as it's updated frequently.
< 
< o  The Handbook and FAQ documents are at http://www.FreeBSD.org/ and,
<    along with the mailing lists, can be searched by going to
<    http://www.FreeBSD.org/search/.  If the doc distribution has
<    been installed, they're also available formatted in /usr/share/doc.
< 
< If you still have a question or problem, please take the output of
< `uname -a', along with any relevant error messages, and email it
< as a question to the questions@FreeBSD.org mailing list.  If you are
< unfamiliar with FreeBSD's directory layout, please refer to the hier(7)
< manual page.  If you are not familiar with manual pages, type `man man'.
< 
< You may also use sysinstall(8) to re-enter the installation and
< configuration utility.  Edit /etc/motd to change this login announcement.
11:52:03
#vi /etc/motd
5,23d4
< Before seeking technical support, please use the following resources:
< 
< o  Security advisories and updated errata information for all releases are
<    at http://www.FreeBSD.org/releases/ - always consult the ERRATA section
<    for your release first as it's updated frequently.
< 
< o  The Handbook and FAQ documents are at http://www.FreeBSD.org/ and,
<    along with the mailing lists, can be searched by going to
<    http://www.FreeBSD.org/search/.  If the doc distribution has
<    been installed, they're also available formatted in /usr/share/doc.
< 
< If you still have a question or problem, please take the output of
< `uname -a', along with any relevant error messages, and email it
< as a question to the questions@FreeBSD.org mailing list.  If you are
< unfamiliar with FreeBSD's directory layout, please refer to the hier(7)
< manual page.  If you are not familiar with manual pages, type `man man'.
< 
< You may also use sysinstall(8) to re-enter the installation and
< configuration utility.  Edit /etc/motd to change this login announcement.
11:52:03
#vi /etc/motd
5,23d4
< Before seeking technical support, please use the following resources:
< 
< o  Security advisories and updated errata information for all releases are
<    at http://www.FreeBSD.org/releases/ - always consult the ERRATA section
<    for your release first as it's updated frequently.
< 
< o  The Handbook and FAQ documents are at http://www.FreeBSD.org/ and,
<    along with the mailing lists, can be searched by going to
<    http://www.FreeBSD.org/search/.  If the doc distribution has
<    been installed, they're also available formatted in /usr/share/doc.
< 
< If you still have a question or problem, please take the output of
< `uname -a', along with any relevant error messages, and email it
< as a question to the questions@FreeBSD.org mailing list.  If you are
< unfamiliar with FreeBSD's directory layout, please refer to the hier(7)
< manual page.  If you are not familiar with manual pages, type `man man'.
< 
< You may also use sysinstall(8) to re-enter the installation and
< configuration utility.  Edit /etc/motd to change this login announcement.
11:52:37
#shutdown -r now
Shutdown NOW!
shutdown: [pid 720]
11:52:37
#shutdown -r now
Shutdown NOW!
shutdown: [pid 720]
11:52:37
#shutdown -r now
Shutdown NOW!
shutdown: [pid 720]
11:52:37
#shutdown -r now
Shutdown NOW!
shutdown: [pid 720]
/dev/ttyv1
11:55:49
#dmesg | less
11:55:49
#dmesg | less
11:55:49
#dmesg | less
11:55:49
#dmesg | less
11:57:18
#dmesg | grep cpu
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
11:57:18
#dmesg | grep cpu
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
11:57:18
#dmesg | grep cpu
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
11:57:18
#dmesg | grep cpu
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
11:57:30
#dmesg | grep i3
pci3: <ACPI PCI bus> on pcib3
uhci3: <UHCI (generic) USB controller> port 0x7000-0x701f irq 19 at device 29.3 on pci0
uhci3: [GIANT-LOCKED]
usb3: <UHCI (generic) USB controller> on uhci3
pci3: <ACPI PCI bus> on pcib3
uhci3: <UHCI (generic) USB controller> port 0x7000-0x701f irq 19 at device 29.3 on pci0
uhci3: [GIANT-LOCKED]
usb3: <UHCI (generic) USB controller> on uhci3
11:57:30
#dmesg | grep i3
pci3: <ACPI PCI bus> on pcib3
uhci3: <UHCI (generic) USB controller> port 0x7000-0x701f irq 19 at device 29.3 on pci0
uhci3: [GIANT-LOCKED]
usb3: <UHCI (generic) USB controller> on uhci3
pci3: <ACPI PCI bus> on pcib3
uhci3: <UHCI (generic) USB controller> port 0x7000-0x701f irq 19 at device 29.3 on pci0
uhci3: [GIANT-LOCKED]
usb3: <UHCI (generic) USB controller> on uhci3
11:57:30
#dmesg | grep i3
pci3: <ACPI PCI bus> on pcib3
uhci3: <UHCI (generic) USB controller> port 0x7000-0x701f irq 19 at device 29.3 on pci0
uhci3: [GIANT-LOCKED]
usb3: <UHCI (generic) USB controller> on uhci3
pci3: <ACPI PCI bus> on pcib3
uhci3: <UHCI (generic) USB controller> port 0x7000-0x701f irq 19 at device 29.3 on pci0
uhci3: [GIANT-LOCKED]
usb3: <UHCI (generic) USB controller> on uhci3
11:57:30
#dmesg | grep i3
pci3: <ACPI PCI bus> on pcib3
uhci3: <UHCI (generic) USB controller> port 0x7000-0x701f irq 19 at device 29.3 on pci0
uhci3: [GIANT-LOCKED]
usb3: <UHCI (generic) USB controller> on uhci3
pci3: <ACPI PCI bus> on pcib3
uhci3: <UHCI (generic) USB controller> port 0x7000-0x701f irq 19 at device 29.3 on pci0
uhci3: [GIANT-LOCKED]
usb3: <UHCI (generic) USB controller> on uhci3
11:57:49
#dmesg | grep i386

11:57:49
#dmesg | grep i386

11:57:49
#dmesg | grep i386

11:57:49
#dmesg | grep i386

11:57:55
#dmesg | grep amd

11:57:55
#dmesg | grep amd

11:57:55
#dmesg | grep amd

11:57:55
#dmesg | grep amd

11:57:59
#dmesg | grep CPU
CPU: Intel(R) Celeron(R) CPU 2.66GHz (2667.00-MHz 686-class CPU)
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
CPU: Intel(R) Celeron(R) CPU 2.66GHz (2667.00-MHz 686-class CPU)
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
11:57:59
#dmesg | grep CPU
CPU: Intel(R) Celeron(R) CPU 2.66GHz (2667.00-MHz 686-class CPU)
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
CPU: Intel(R) Celeron(R) CPU 2.66GHz (2667.00-MHz 686-class CPU)
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
11:57:59
#dmesg | grep CPU
CPU: Intel(R) Celeron(R) CPU 2.66GHz (2667.00-MHz 686-class CPU)
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
CPU: Intel(R) Celeron(R) CPU 2.66GHz (2667.00-MHz 686-class CPU)
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
11:57:59
#dmesg | grep CPU
CPU: Intel(R) Celeron(R) CPU 2.66GHz (2667.00-MHz 686-class CPU)
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
CPU: Intel(R) Celeron(R) CPU 2.66GHz (2667.00-MHz 686-class CPU)
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
11:58:05
#dmesg | grep memory
real memory  = 2138701824 (2039 MB)
avail memory = 2088042496 (1991 MB)
atapci2: failed to enable memory mapping!
real memory  = 2138701824 (2039 MB)
avail memory = 2088042496 (1991 MB)
atapci2: failed to enable memory mapping!
11:58:05
#dmesg | grep memory
real memory  = 2138701824 (2039 MB)
avail memory = 2088042496 (1991 MB)
atapci2: failed to enable memory mapping!
real memory  = 2138701824 (2039 MB)
avail memory = 2088042496 (1991 MB)
atapci2: failed to enable memory mapping!
11:58:05
#dmesg | grep memory
real memory  = 2138701824 (2039 MB)
avail memory = 2088042496 (1991 MB)
atapci2: failed to enable memory mapping!
real memory  = 2138701824 (2039 MB)
avail memory = 2088042496 (1991 MB)
atapci2: failed to enable memory mapping!
11:58:05
#dmesg | grep memory
real memory  = 2138701824 (2039 MB)
avail memory = 2088042496 (1991 MB)
atapci2: failed to enable memory mapping!
real memory  = 2138701824 (2039 MB)
avail memory = 2088042496 (1991 MB)
atapci2: failed to enable memory mapping!
прошло 12 минут
/dev/ttyv2
12:10:20
#ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=b<RXCSUM,TXCSUM,VLAN_MTU>
        inet6 fe80::213:d4ff:feb2:4fec%em0 prefixlen 64 scopeid 0x1
        inet 192.168.15.26 netmask 0xffffff00 broadcast 192.168.15.255
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
xl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        options=9<RXCSUM,VLAN_MTU>
        ether 00:04:79:67:96:71
        media: Ethernet autoselect (none)
        status: no carrier
plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
        inet 127.0.0.1 netmask 0xff000000
12:10:20
#ifconfig
exit
exit
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=b<RXCSUM,TXCSUM,VLAN_MTU>
        inet6 fe80::213:d4ff:feb2:4fec%em0 prefixlen 64 scopeid 0x1
        inet 192.168.15.26 netmask 0xffffff00 broadcast 192.168.15.255
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
xl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        options=9<RXCSUM,VLAN_MTU>
        ether 00:04:79:67:96:71
        media: Ethernet autoselect (none)
        status: no carrier
plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
        inet 127.0.0.1 netmask 0xff000000
12:10:20
#ifconfig
exit
exit
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=b<RXCSUM,TXCSUM,VLAN_MTU>
        inet6 fe80::213:d4ff:feb2:4fec%em0 prefixlen 64 scopeid 0x1
        inet 192.168.15.26 netmask 0xffffff00 broadcast 192.168.15.255
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
xl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        options=9<RXCSUM,VLAN_MTU>
        ether 00:04:79:67:96:71
        media: Ethernet autoselect (none)
        status: no carrier
plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
        inet 127.0.0.1 netmask 0xff000000
12:10:20
#ifconfig
exit
exit
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=b<RXCSUM,TXCSUM,VLAN_MTU>
        inet6 fe80::213:d4ff:feb2:4fec%em0 prefixlen 64 scopeid 0x1
        inet 192.168.15.26 netmask 0xffffff00 broadcast 192.168.15.255
        ether 00:13:d4:b2:4f:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
xl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        options=9<RXCSUM,VLAN_MTU>
        ether 00:04:79:67:96:71
        media: Ethernet autoselect (none)
        status: no carrier
plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
        inet 127.0.0.1 netmask 0xff000000
12:10:23
#vi /etc/rc.conf
12:10:23
#vi /etc/rc.conf
12:10:23
#vi /etc/rc.conf
12:10:23
#vi /etc/rc.conf
12:11:40
#vi /etc/servises
12:11:40
#vi /etc/servises
12:11:40
#vi /etc/servises
12:11:40
#vi /etc/servises
12:17:35
#vi /etc/services
12:17:35
#vi /etc/services
12:17:35
#vi /etc/services
12:17:35
#vi /etc/services
12:20:23
#sockstat -4l
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
root     sendmail   442   4  tcp4   127.0.0.1:25          *:*
root     sshd       436   4  tcp4   *:22                  *:*
root     syslogd    310   6  udp4   *:514                 *:*
12:20:23
#sockstat -4l
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
root     sendmail   442   4  tcp4   127.0.0.1:25          *:*
root     sshd       436   4  tcp4   *:22                  *:*
root     syslogd    310   6  udp4   *:514                 *:*
12:20:23
#sockstat -4l
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
root     sendmail   442   4  tcp4   127.0.0.1:25          *:*
root     sshd       436   4  tcp4   *:22                  *:*
root     syslogd    310   6  udp4   *:514                 *:*
12:20:23
#sockstat -4l
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
root     sendmail   442   4  tcp4   127.0.0.1:25          *:*
root     sshd       436   4  tcp4   *:22                  *:*
root     syslogd    310   6  udp4   *:514                 *:*
12:21:53
#sockstat -4
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
user     ssh        1073  3  tcp4   192.168.15.26:62610   192.168.15.23:22
root     sendmail   442   4  tcp4   127.0.0.1:25          *:*
root     sshd       436   4  tcp4   *:22                  *:*
root     syslogd    310   6  udp4   *:514                 *:*
12:21:53
#sockstat -4
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
user     ssh        1073  3  tcp4   192.168.15.26:62610   192.168.15.23:22
root     sendmail   442   4  tcp4   127.0.0.1:25          *:*
root     sshd       436   4  tcp4   *:22                  *:*
root     syslogd    310   6  udp4   *:514                 *:*
12:21:53
#sockstat -4
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
user     ssh        1073  3  tcp4   192.168.15.26:62610   192.168.15.23:22
root     sendmail   442   4  tcp4   127.0.0.1:25          *:*
root     sshd       436   4  tcp4   *:22                  *:*
root     syslogd    310   6  udp4   *:514                 *:*
12:21:53
#sockstat -4
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
user     ssh        1073  3  tcp4   192.168.15.26:62610   192.168.15.23:22
root     sendmail   442   4  tcp4   127.0.0.1:25          *:*
root     sshd       436   4  tcp4   *:22                  *:*
root     syslogd    310   6  udp4   *:514                 *:*
12:22:52
#sockstat -4
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
user     ssh        1073  3  tcp4   192.168.15.26:62610   192.168.15.23:22
root     sendmail   442   4  tcp4   127.0.0.1:25          *:*
root     sshd       436   4  tcp4   *:22                  *:*
root     syslogd    310   6  udp4   *:514                 *:*
12:22:52
#sockstat -4
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
user     ssh        1073  3  tcp4   192.168.15.26:62610   192.168.15.23:22
root     sendmail   442   4  tcp4   127.0.0.1:25          *:*
root     sshd       436   4  tcp4   *:22                  *:*
root     syslogd    310   6  udp4   *:514                 *:*
12:22:52
#sockstat -4
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
user     ssh        1073  3  tcp4   192.168.15.26:62610   192.168.15.23:22
root     sendmail   442   4  tcp4   127.0.0.1:25          *:*
root     sshd       436   4  tcp4   *:22                  *:*
root     syslogd    310   6  udp4   *:514                 *:*
12:22:52
#sockstat -4
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
user     ssh        1073  3  tcp4   192.168.15.26:62610   192.168.15.23:22
root     sendmail   442   4  tcp4   127.0.0.1:25          *:*
root     sshd       436   4  tcp4   *:22                  *:*
root     syslogd    310   6  udp4   *:514                 *:*
12:25:22
#pkg_add -r nmap
Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.0-release/Latest/nmap.tbz: File unavailable (e.g., file not found, no access)
pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.0-release/Latest/nmap.tbz' by URL
12:25:22
#pkg_add -r nmap
Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.0-release/Latest/nmap.tbz: File unavailable (e.g., file not found, no access)
pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.0-release/Latest/nmap.tbz' by URL
12:25:22
#pkg_add -r nmap
Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.0-release/Latest/nmap.tbz: File unavailable (e.g., file not found, no access)
pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.0-release/Latest/nmap.tbz' by URL
12:25:22
#pkg_add -r nmap
Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.0-release/Latest/nmap.tbz: File unavailable (e.g., file not found, no access)
pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.0-release/Latest/nmap.tbz' by URL
12:26:37
#cd /usr/ports/security/nmap

12:26:37
#cd /usr/ports/security/nmap

12:26:37
#cd /usr/ports/security/nmap

12:26:37
#cd /usr/ports/security/nmap

12:26:56
#make install
checking for snprintf... (cached) yes
checking for asprintf... yes
checking for asnprintf... no
checking for vasprintf... yes
checking for vasnprintf... no
checking for usleep... yes
checking for gettimeofday... yes
checking for sleep... yes
checking for getopt_long_only... yes
checking for strcasecmp... (cached) yes
...
      This port has installed the following files which may act as network
      servers and may therefore pose a remote security risk to the system.
/usr/local/bin/nmap
      If there are vulnerabilities in these programs there may be a security
      risk to the system. FreeBSD makes no guarantee about the security of
      ports included in the Ports Collection. Please type 'make deinstall'
      to deinstall the port if this is a concern.
      For more information, and contact details about the security
      status of this software, see the following webpage:
http://www.insecure.org/nmap/
12:26:56
#make install
checking for snprintf... (cached) yes
checking for asprintf... yes
checking for asnprintf... no
checking for vasprintf... yes
checking for vasnprintf... no
checking for usleep... yes
checking for gettimeofday... yes
checking for sleep... yes
checking for getopt_long_only... yes
checking for strcasecmp... (cached) yes
...
      This port has installed the following files which may act as network
      servers and may therefore pose a remote security risk to the system.
/usr/local/bin/nmap
      If there are vulnerabilities in these programs there may be a security
      risk to the system. FreeBSD makes no guarantee about the security of
      ports included in the Ports Collection. Please type 'make deinstall'
      to deinstall the port if this is a concern.
      For more information, and contact details about the security
      status of this software, see the following webpage:
http://www.insecure.org/nmap/
12:26:56
#make install
checking for snprintf... (cached) yes
checking for asprintf... yes
checking for asnprintf... no
checking for vasprintf... yes
checking for vasnprintf... no
checking for usleep... yes
checking for gettimeofday... yes
checking for sleep... yes
checking for getopt_long_only... yes
checking for strcasecmp... (cached) yes
...
      This port has installed the following files which may act as network
      servers and may therefore pose a remote security risk to the system.
/usr/local/bin/nmap
      If there are vulnerabilities in these programs there may be a security
      risk to the system. FreeBSD makes no guarantee about the security of
      ports included in the Ports Collection. Please type 'make deinstall'
      to deinstall the port if this is a concern.
      For more information, and contact details about the security
      status of this software, see the following webpage:
http://www.insecure.org/nmap/
12:26:56
#make install
checking for snprintf... (cached) yes
checking for asprintf... yes
checking for asnprintf... no
checking for vasprintf... yes
checking for vasnprintf... no
checking for usleep... yes
checking for gettimeofday... yes
checking for sleep... yes
checking for getopt_long_only... yes
checking for strcasecmp... (cached) yes
...
      This port has installed the following files which may act as network
      servers and may therefore pose a remote security risk to the system.
/usr/local/bin/nmap
      If there are vulnerabilities in these programs there may be a security
      risk to the system. FreeBSD makes no guarantee about the security of
      ports included in the Ports Collection. Please type 'make deinstall'
      to deinstall the port if this is a concern.
      For more information, and contact details about the security
      status of this software, see the following webpage:
http://www.insecure.org/nmap/

Статистика

Время первой команды журнала19:45:17 2006-11-27
Время последней команды журнала12:26:56 2006-11-28
Количество командных строк в журнале101
Процент команд с ненулевым кодом завершения, %28.71
Процент синтаксически неверно набранных команд, % 0.00
Суммарное время работы с терминалом *, час 0.87
Количество командных строк в единицу времени, команда/мин 1.94
Частота использования команд
dmesg28|=====================| 21.71%
grep24|==================| 18.60%
vi16|============| 12.40%
ping13|==========| 10.08%
sockstat12|=========| 9.30%
ifconfig8|======| 6.20%
shutdown8|======| 6.20%
[root@fbsd6:~]#4|===| 3.10%
less4|===| 3.10%
pkg_add4|===| 3.10%
make4|===| 3.10%
cd4|===| 3.10%
____
*) Интервалы неактивности длительностью 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$