/l3/users/My-Debian-Work/adm.prombez/ol14 :1 :2 :3 :4 :5 :6 :7 :8 :9 :10 :11 :12 :13 :14 :15 :16 :17 :18 :19 :20 :21 :22 :23 :24 |
$mysql -h localhost -u root -p12qw#12qw ntddb
206 rdesktop -uol14 -p13r@7t -g1024x768 -a16 -k en-us.fixed 192.168.0.2 |
$ping ya.ru
connect: Network is unreachable |
$ping 192.168.0.126
PING 192.168.0.126 (192.168.0.126) 56(84) bytes of data. 64 bytes from 192.168.0.126: icmp_seq=1 ttl=64 time=0.288 ms 64 bytes from 192.168.0.126: icmp_seq=2 ttl=64 time=0.294 ms 64 bytes from 192.168.0.126: icmp_seq=3 ttl=64 time=0.291 ms 64 bytes from 192.168.0.126: icmp_seq=4 ttl=64 time=0.318 ms 64 bytes from 192.168.0.126: icmp_seq=5 ttl=64 time=0.282 ms 64 bytes from 192.168.0.126: icmp_seq=6 ttl=64 time=0.286 ms 64 bytes from 192.168.0.126: icmp_seq=7 ttl=64 time=0.290 ms ^X64 bytes from 192.168.0.126: icmp_seq=8 ttl=64 time=0.313 ms ^Z [1]+ Stopped ping 192.168.0.126 |
$ping 193.138.131.107
connect: Network is unreachable |
$ping 192.168.0.200
PING 192.168.0.200 (192.168.0.200) 56(84) bytes of data. 64 bytes from 192.168.0.200: icmp_seq=1 ttl=128 time=0.249 ms 64 bytes from 192.168.0.200: icmp_seq=2 ttl=128 time=0.262 ms 64 bytes from 192.168.0.200: icmp_seq=3 ttl=128 time=0.231 ms ^Z [1]+ Stopped ping 192.168.0.200 |
$ping iserver
PING iserver.prombez (192.168.0.126) 56(84) bytes of data. 64 bytes from squid-stat.prombez (192.168.0.126): icmp_seq=1 ttl=64 time=0.293 ms 64 bytes from lightsquid.prombez (192.168.0.126): icmp_seq=2 ttl=64 time=0.291 ms 64 bytes from mediawiki.prombez (192.168.0.126): icmp_seq=3 ttl=64 time=0.303 ms 64 bytes from iserver.prombez (192.168.0.126): icmp_seq=4 ttl=64 time=0.307 ms 64 bytes from vnstat.prombez (192.168.0.126): icmp_seq=5 ttl=64 time=0.279 ms 64 bytes from squid-stat.prombez (192.168.0.126): icmp_seq=6 ttl=64 time=0.291 ms 64 bytes from lightsquid.prombez (192.168.0.126): icmp_seq=7 ttl=64 time=0.296 ms 64 bytes from mediawiki.prombez (192.168.0.126): icmp_seq=8 ttl=64 time=0.299 ms 64 bytes from iserver.prombez (192.168.0.126): icmp_seq=9 ttl=64 time=0.316 ms 64 bytes from vnstat.prombez (192.168.0.126): icmp_seq=10 ttl=64 time=0.326 ms 64 bytes from squid-stat.prombez (192.168.0.126): icmp_seq=11 ttl=64 time=0.292 ms 64 bytes from lightsquid.prombez (192.168.0.126): icmp_seq=12 ttl=64 time=0.303 ms 64 bytes from mediawiki.prombez (192.168.0.126): icmp_seq=13 ttl=64 time=0.278 ms 64 bytes from iserver.prombez (192.168.0.126): icmp_seq=14 ttl=64 time=0.326 ms ^X^Z [1]+ Stopped ping iserver |
$ping 74.ru
PING 74.ru (195.54.18.102) 56(84) bytes of data. 64 bytes from host102.dc-chel.w.rugion.ru (195.54.18.102): icmp_seq=1 ttl=57 time=3.42 ms 64 bytes from host102.dc-chel.w.rugion.ru (195.54.18.102): icmp_seq=2 ttl=57 time=2.13 ms 64 bytes from host102.dc-chel.w.rugion.ru (195.54.18.102): icmp_seq=3 ttl=57 time=2.49 ms 64 bytes from host102.dc-chel.w.rugion.ru (195.54.18.102): icmp_seq=4 ttl=57 time=3.34 ms ^X64 bytes from host102.dc-chel.w.rugion.ru (195.54.18.102): icmp_seq=5 ttl=57 time=2.81 ms 64 bytes from host102.dc-chel.w.rugion.ru (195.54.18.102): icmp_seq=6 ttl=57 time=2.97 ms ^Z [2]+ Stopped ping 74.ru |
$ping ya.ru
PING ya.ru (87.250.250.3) 56(84) bytes of data. 64 bytes from www.yandex.ru (87.250.250.3): icmp_seq=1 ttl=56 time=30.7 ms 64 bytes from www.yandex.ru (87.250.250.3): icmp_seq=2 ttl=56 time=28.9 ms 64 bytes from www.yandex.ru (87.250.250.3): icmp_seq=3 ttl=56 time=28.8 ms ^X64 bytes from www.yandex.ru (87.250.250.3): icmp_seq=4 ttl=56 time=29.3 ms 64 bytes from www.yandex.ru (87.250.250.3): icmp_seq=5 ttl=56 time=30.1 ms 64 bytes from www.yandex.ru (87.250.250.3): icmp_seq=6 ttl=56 time=29.3 ms 64 bytes from www.yandex.ru (87.250.250.3): icmp_seq=7 ttl=56 time=29.2 ms 64 bytes from www.yandex.ru (87.250.250.3): icmp_seq=8 ttl=56 time=29.0 ms 64 bytes from www.yandex.ru (87.250.250.3): icmp_seq=9 ttl=56 time=29.6 ms ^Z [3]+ Stopped ping ya.ru |
$ssh ol14@192.168.0.4
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is a0:a0:70:1a:19:65:7d:d1:ba:21:08:a2:9b:e1:2e:18. Please contact your system administrator. Add correct host key in /home/ol14/.ssh/known_hosts to get rid of this message. Offending key in /home/ol14/.ssh/known_hosts:8 RSA host key for 192.168.0.4 has changed and you have requested strict checking. Host key verification failed. |
$ssh root@192.168.0.4
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is a0:a0:70:1a:19:65:7d:d1:ba:21:08:a2:9b:e1:2e:18. Please contact your system administrator. Add correct host key in /home/ol14/.ssh/known_hosts to get rid of this message. Offending key in /home/ol14/.ssh/known_hosts:8 RSA host key for 192.168.0.4 has changed and you have requested strict checking. Host key verification failed. |
$ÑÑssh ol14@192.168.0.4
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is a0:a0:70:1a:19:65:7d:d1:ba:21:08:a2:9b:e1:2e:18. Please contact your system administrator. Add correct host key in /home/ol14/.ssh/known_hosts to get rid of this message. Offending key in /home/ol14/.ssh/known_hosts:8 RSA host key for 192.168.0.4 has changed and you have requested strict checking. Host key verification failed. |
$ssh ol14@192.168.0.4
200 rdesktop -uol14 -p13r@7t -g1024x768 -a16 -k en-us.fixed 192.168.0.2 |
$ol14 -p13r@7t -g1024x768 -a16 -k en-us.fixed 192.168.0.200
WARNING: No translation for (keysym 0x2f, slash) WARNING: No translation for (keysym 0x2f, slash) WARNING: No translation for (keysym 0x5c, backslash) WARNING: No translation for (keysym 0x5c, backslash) WARNING: No translation for (keysym 0x5c, backslash) WARNING: No translation for (keysym 0x5c, backslash) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) ... WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0xfe0a, ISO_Prev_Group) WARNING: No translation for (keysym 0x6cb, Cyrillic_ka) WARNING: No translation for (keysym 0x6cb, Cyrillic_ka) WARNING: No translation for (keysym 0x22, quotedbl) WARNING: No translation for (keysym 0x6c5, Cyrillic_ie) WARNING: No translation for (keysym 0x6c5, Cyrillic_ie) |
$ping 192.168.0.55
|
$su
|
$ssh ol14@192.168.0.4
|
$ping ya.ru
|
$ping 192.168.0.200
|
$su
|
$ifconfig eth0
|
$ping ya.ru
|
$mysql -h localhost -u root -p12qw#12qw ntddb
|
$iat /media/arhiv2/civ4.mdf /media/arhiv2/civ4.iso
Iso9660 Analyzer Tool v0.1.3 by Salvatore Santagati Licensed under GPL v2 or later Image is broken This image is not CD IMAGE |
$uname -a
Linux adm 2.6.26-2-686 #1 SMP Thu Jan 27 00:28:05 UTC 2011 i686 GNU/Linux |
$ssh ol14@192.168.0.240
ssh: connect to host 192.168.0.240 port 22: No route to host |
$ssh -p13r@7t ol14@192.168.0.240
Bad port '13r@7t' |
$ssh ol14@192.168.0.240
ssh: connect to host 192.168.0.240 port 22: No route to host |
$ssh ol14@192.168.0.243
~ ~ ~ "/etc/hosts" 10L, 270C written debian:/home/ol14# cat /etc/hosts 127.0.0.1 localhost 192.168.0.150 pdc.prombez.chel pdc # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ... ~ ~ ~ ~ "/etc/resolv.conf" 3L, 65C written debian:/home/ol14# reboot Broadcast message from root@debian (pts/0) (Tue Jun 7 16:53:45 2011): The system is going down for reboot NOW! debian:/home/ol14# Connection to 192.168.0.243 closed by remote host. Connection to 192.168.0.243 closed. |
$ssh ol14@192.168.0.150
РаÑпаковÑваеÑÑÑ Ð¿Ð°ÐºÐµÑ dcc-common (из Ñайла dcc-common_1.2.74-2_i386.deb)... ÐаÑÑÑаиваеÑÑÑ Ð¿Ð°ÐºÐµÑ dcc-client (1.2.74-2) ... chown: невеÑнÑй полÑзоваÑелÑ: `dcc.dcc' chown: невеÑнÑй полÑзоваÑелÑ: `dcc.dcc' update-rc.d: warning: /etc/init.d/dcc-client missing LSB information update-rc.d: see <http://wiki.debian.org/LSBInitScripts> Starting DCC program interface daemon: dccifdstart-stop-daemon: group `dcc' not found (Success) invoke-rc.d: initscript dcc-client, action "start" failed. ÐбÑабаÑÑваÑÑÑÑ ÑÑиггеÑÑ Ð´Ð»Ñ man-db ... ... â â â ââ â â â â â â ââ â â â â â â ââ â â â â â â ââ â â â â â â ââ â â â â â â ââ â â â ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ¾ââââââââââââââââââââââââââââââââââââ â slapd.conf ââ syslog â ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ СовеÑ: ХоÑиÑе пÑоÑÑÑÑ Ð¾Ð±Ð¾Ð»Ð¾ÑкÑ? ÐажмиÑе C-o, и Ñнова C-o Ð´Ð»Ñ Ð²Ð¾Ð·Ð²ÑаÑа в ÐС. |
$buhgalt3 -p1 -g1024x768 -a16 -k en-us.fixed 192.168.0.75
WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2f, slash) WARNING: No translation for (keysym 0x2f, slash) WARNING: No translation for (keysym 0x2e, period) WARNING: No translation for (keysym 0x2e, period) |
$htop
ssh ol14@192.168.0.150 ssh: connect to host 192.168.0.150 port 22: Connection refused |
$ssh ol14@192.168.0.150
# # Sample configuration file for the Samba suite for Debian GNU/Linux. # # # This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options most of which "/etc/samba/smb.conf" 326L, 11919C GNU nano 2.0.7 Файл: /etc/samba/smb.conf Ðзменен workgroup = PROMBEZ ... â sshd â 1272âФев 8 2008 ââ â â â â sudo â 119âÐÑн 11 2010 ââ â â â â â â ââ â â â â â â ââ â â â ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ¾ââââââââââââââââââââââââââââââââââââââââââââ ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ pdc:/home/ol14# reboot The system is going down for reboot NOW!chel (pts/0) (Thu Jun 9 14:29:11 201 pdc:/home/ol14# Connection to 192.168.0.150 closed by remote host. Connection to 192.168.0.150 closed. |
$ssh ol14@192.168.0.150
ssh: connect to host 192.168.0.150 port 22: No route to host |
$su
Пароль: su: Сбой при проверке подлинности |
$ping 192.168.0.70
PING 192.168.0.70 (192.168.0.70) 56(84) bytes of data. 64 bytes from 192.168.0.70: icmp_seq=1 ttl=128 time=1.03 ms 64 bytes from 192.168.0.70: icmp_seq=2 ttl=128 time=0.624 ms 64 bytes from 192.168.0.70: icmp_seq=3 ttl=128 time=0.626 ms 64 bytes from 192.168.0.70: icmp_seq=4 ttl=128 time=0.590 ms 64 bytes from 192.168.0.70: icmp_seq=5 ttl=128 time=0.667 ms 64 bytes from 192.168.0.70: icmp_seq=6 ttl=128 time=0.637 ms 64 bytes from 192.168.0.70: icmp_seq=7 ttl=128 time=0.653 ms 64 bytes from 192.168.0.70: icmp_seq=8 ttl=128 time=0.647 ms 64 bytes from 192.168.0.70: icmp_seq=9 ttl=128 time=0.562 ms ... 64 bytes from 192.168.0.70: icmp_seq=14 ttl=128 time=0.644 ms 64 bytes from 192.168.0.70: icmp_seq=15 ttl=128 time=0.652 ms 64 bytes from 192.168.0.70: icmp_seq=16 ttl=128 time=0.617 ms 64 bytes from 192.168.0.70: icmp_seq=17 ttl=128 time=0.569 ms 64 bytes from 192.168.0.70: icmp_seq=18 ttl=128 time=0.655 ms 64 bytes from 192.168.0.70: icmp_seq=19 ttl=128 time=0.633 ms 64 bytes from 192.168.0.70: icmp_seq=20 ttl=128 time=0.666 ms 64 bytes from 192.168.0.70: icmp_seq=21 ttl=128 time=0.666 ms ^Z [1]+ Stopped ping 192.168.0.70 |
$ping buhg15-1
ping: unknown host buhg15-1 |
$ping buhg-15-1
PING buhg-15-1.prombez (192.168.0.70) 56(84) bytes of data. 64 bytes from buhg-15-1.prombez (192.168.0.70): icmp_seq=1 ttl=128 time=0.622 ms 64 bytes from buhg-15-1.prombez (192.168.0.70): icmp_seq=2 ttl=128 time=0.637 ms 64 bytes from buhg-15-1.prombez (192.168.0.70): icmp_seq=3 ttl=128 time=0.616 ms 64 bytes from buhg-15-1.prombez (192.168.0.70): icmp_seq=4 ttl=128 time=0.625 ms 64 bytes from buhg-15-1.prombez (192.168.0.70): icmp_seq=5 ttl=128 time=0.560 ms 64 bytes from buhg-15-1.prombez (192.168.0.70): icmp_seq=6 ttl=128 time=0.575 ms 64 bytes from buhg-15-1.prombez (192.168.0.70): icmp_seq=7 ttl=128 time=0.601 ms 64 bytes from buhg-15-1.prombez (192.168.0.70): icmp_seq=8 ttl=128 time=0.649 ms 64 bytes from buhg-15-1.prombez (192.168.0.70): icmp_seq=9 ttl=128 time=0.630 ms 64 bytes from buhg-15-1.prombez (192.168.0.70): icmp_seq=10 ttl=128 time=0.636 ms ^Z [2]+ Stopped ping buhg-15-1 |
$rdesktop -uol14 -p13r@7t -g1024x768 -a16 -k en-us.fixed 192.168.0.70
^Z [2]+ Stopped rdesktop -uol14 -p13r@7t -g1024x768 -a16 -k en-us.fixed 192.168.0.70 |
$rdesktop -uol14 -p13r@7t -g1024x768 -a16 -k en-us.fixed 192.168.0.70
|
$зшrdesktop -uol14 -p13r@7t -g1024x768 -a16 -k en-us.fixed 192.168.0.55
|
$ping 192.168.0.55
PING 192.168.0.55 (192.168.0.55) 56(84) bytes of data. 64 bytes from 192.168.0.55: icmp_seq=1 ttl=128 time=2.51 ms 64 bytes from 192.168.0.55: icmp_seq=2 ttl=128 time=0.281 ms 64 bytes from 192.168.0.55: icmp_seq=3 ttl=128 time=0.304 ms ^Z [1]+ Stopped ping 192.168.0.55 |
$ssh ol14@192.168.0.150
|
$htop
|
$mysql -h localhost -u root -p12qw#12qw ntddb
Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 256 Server version: 5.0.51a-24+lenny5 (Debian) Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> select * FROM countpages ; +----+-----------+--------+------+-----------------------------------------------------+------------+ | id | allvisits | visits | uniq | iplist | dat | +----+-----------+--------+------+-----------------------------------------------------+------------+ ... | 3 | 198 | 34 | 1 | 192.168.0.127; | 2011-06-07 | | 4 | 206 | 8 | 4 | 192.168.0.127;192.168.0.132;127.0.0.1;192.168.0.88; | 2011-06-08 | | 5 | 212 | 6 | 1 | 192.168.0.127; | 2011-06-09 | | 6 | 214 | 2 | 1 | 192.168.0.127; | 2011-06-10 | | 7 | 234 | 20 | 2 | 192.168.0.127;192.168.0.43; | 2011-06-14 | | 8 | 236 | 2 | 1 | 192.168.0.127; | 2011-06-15 | +----+-----------+--------+------+-----------------------------------------------------+------------+ 8 rows in set (0.00 sec) mysql> quit Bye |
$ping 192.168.0.126
PING 192.168.0.126 (192.168.0.126) 56(84) bytes of data. ^Z [1]+ Stopped ping 192.168.0.126 |
$mysql -h localhost -u root -p12qw#12qw ntddb
Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 289 Server version: 5.0.51a-24+lenny5 (Debian) Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> select * FROM countpages ; +----+-----------+--------+------+-----------------------------------------------------+------------+ | id | allvisits | visits | uniq | iplist | dat | +----+-----------+--------+------+-----------------------------------------------------+------------+ ... | 5 | 212 | 6 | 1 | 192.168.0.127; | 2011-06-09 | | 6 | 214 | 2 | 1 | 192.168.0.127; | 2011-06-10 | | 7 | 234 | 20 | 2 | 192.168.0.127;192.168.0.43; | 2011-06-14 | | 8 | 253 | 19 | 2 | 192.168.0.127;192.168.0.69; | 2011-06-15 | | 9 | 263 | 10 | 1 | 192.168.0.127; | 2011-06-16 | | 10 | 268 | 5 | 2 | 192.168.0.127;127.0.0.1; | 2011-06-17 | +----+-----------+--------+------+-----------------------------------------------------+------------+ 10 rows in set (0.00 sec) mysql> quit Bye |
$mysql -h localhost -u root -p12qw#12qw ntddb
Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 306 Server version: 5.0.51a-24+lenny5 (Debian) Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> quit Bye |
$telnet 192.168.0.55
Trying 192.168.0.55... telnet: Unable to connect to remote host: Connection refused |
$telnet 192.168.0.89
Trying 192.168.0.89... telnet: Unable to connect to remote host: Connection refused |
$telnet 192.168.0.90
Trying 192.168.0.90... ^Z^X^Z^C |
$telnet 192.168.0.200
Trying 192.168.0.200... telnet: Unable to connect to remote host: Connection refused |
$telnet 192.168.0.88
Trying 192.168.0.88... telnet: Unable to connect to remote host: Connection refused |
$telnet 192.168.0.887
telnet: could not resolve 192.168.0.887/telnet: Name or service not known |
$telnet 192.168.0.87
Trying 192.168.0.87... ^Zq^Z^X^C |
$telnet 192.168.0.87:25
telnet: could not resolve 192.168.0.87:25/telnet: Name or service not known |
$telnet 192.168.0.87:80
telnet: could not resolve 192.168.0.87:80/telnet: Name or service not known |
$telnet 192.168.0.126:80
telnet: could not resolve 192.168.0.126:80/telnet: Name or service not known |
$telnet 192.168.0.126:21
telnet: could not resolve 192.168.0.126:21/telnet: Name or service not known |
$uname -a
Linux adm 2.6.26-2-686 #1 SMP Sat Jun 11 14:54:10 UTC 2011 i686 GNU/Linux |
$яфд5671
bash: яфд5671: команда не найдена |
$root
bash: root: команда не найдена |
$root
bash: root: команда не найдена |
$su
Пароль: su: Сбой при проверке подлинности |
$ping 192.168.0.15
PING 192.168.0.15 (192.168.0.15) 56(84) bytes of data. From 192.168.0.127 icmp_seq=1 Destination Host Unreachable From 192.168.0.127 icmp_seq=2 Destination Host Unreachable From 192.168.0.127 icmp_seq=3 Destination Host Unreachable From 192.168.0.127 icmp_seq=4 Destination Host Unreachable From 192.168.0.127 icmp_seq=5 Destination Host Unreachable From 192.168.0.127 icmp_seq=6 Destination Host Unreachable From 192.168.0.127 icmp_seq=7 Destination Host Unreachable From 192.168.0.127 icmp_seq=8 Destination Host Unreachable From 192.168.0.127 icmp_seq=9 Destination Host Unreachable ^Z [1]+ Stopped ping 192.168.0.15 |
$ipconf -a
bash: ipconf: команда не найдена |
$ping 193.131.138.124
PING 193.131.138.124 (193.131.138.124) 56(84) bytes of data. From 193.131.159.2 icmp_seq=1 Time to live exceeded From 193.131.159.2 icmp_seq=2 Time to live exceeded From 193.131.159.2 icmp_seq=3 Time to live exceeded From 193.131.159.2 icmp_seq=4 Time to live exceeded ^Z [1]+ Stopped ping 193.131.138.124 |
$ping 193.138.131.124
PING 193.138.131.124 (193.138.131.124) 56(84) bytes of data. 64 bytes from 193.138.131.124: icmp_seq=1 ttl=64 time=0.330 ms 64 bytes from 193.138.131.124: icmp_seq=2 ttl=64 time=0.287 ms 64 bytes from 193.138.131.124: icmp_seq=3 ttl=64 time=0.294 ms ^Z [2]+ Stopped ping 193.138.131.124 |
$ping 193.138.131.107
PING 193.138.131.107 (193.138.131.107) 56(84) bytes of data. 64 bytes from 193.138.131.107: icmp_seq=2 ttl=63 time=5.30 ms 64 bytes from 193.138.131.107: icmp_seq=3 ttl=63 time=4.08 ms 64 bytes from 193.138.131.107: icmp_seq=4 ttl=63 time=3.77 ms ^Z [3]+ Stopped ping 193.138.131.107 |
$ping 193.138.131.107
PING 193.138.131.107 (193.138.131.107) 56(84) bytes of data. 64 bytes from 193.138.131.107: icmp_seq=1 ttl=63 time=1016 ms 64 bytes from 193.138.131.107: icmp_seq=2 ttl=63 time=19.0 ms 64 bytes from 193.138.131.107: icmp_seq=3 ttl=63 time=23.0 ms 64 bytes from 193.138.131.107: icmp_seq=4 ttl=63 time=6.98 ms 64 bytes from 193.138.131.107: icmp_seq=5 ttl=63 time=64.1 ms 64 bytes from 193.138.131.107: icmp_seq=6 ttl=63 time=84.4 ms 64 bytes from 193.138.131.107: icmp_seq=7 ttl=63 time=39.1 ms ^Z [4]+ Stopped ping 193.138.131.107 |
$mc
|
$ping 192.168.0.126
|
$uname -a
Linux adm 2.6.26-2-686 #1 SMP Sat Jun 11 14:54:10 UTC 2011 i686 GNU/Linux |
$ssh ol14@mytest.prombez
The authenticity of host 'mytest.prombez (192.168.0.150)' can't be established. RSA key fingerprint is 02:97:d8:d2:63:62:4f:16:7e:1d:35:d3:b6:a2:a5:42. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'mytest.prombez' (RSA) to the list of known hosts. Warning: the RSA host key for 'mytest.prombez' differs from the key for the IP address '192.168.0.150' Offending key for IP in /home/ol14/.ssh/known_hosts:10 Are you sure you want to continue connecting (yes/no)? y Please type 'yes' or 'no': yes ol14@mytest.prombez's password: Linux mytest 2.6.32-5-686 #1 SMP Mon Jun 13 04:13:06 UTC 2011 i686 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. You have mail. ol14@mytest:~$ exit logout Connection to mytest.prombez closed. |
$ssh-copy-id"ol14@192.168.0.150"
bash: ssh-copy-idol14@192.168.0.150: команда не найдена |
$ssh-copy-id "ol14@192.168.0.150"
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is 02:97:d8:d2:63:62:4f:16:7e:1d:35:d3:b6:a2:a5:42. Please contact your system administrator. Add correct host key in /home/ol14/.ssh/known_hosts to get rid of this message. Offending key in /home/ol14/.ssh/known_hosts:10 RSA host key for 192.168.0.150 has changed and you have requested strict checking. Host key verification failed. |
$ssh-copy-id "ol14@192.168.0.150"
ol14@mytest.prombez Warning: the RSA host key for 'mytest.prombez' differs from the key for the IP address '192.168.0.150' Offending key for IP in /home/ol14/.ssh/known_hosts:10 Matching host key in /home/ol14/.ssh/known_hosts:11 Are you sure you want to continue connecting (yes/no)? yes Permission denied (publickey). |
$ssh ol14@mytest.prombez
Warning: the RSA host key for 'mytest.prombez' differs from the key for the IP address '192.168.0.150' Offending key for IP in /home/ol14/.ssh/known_hosts:10 Matching host key in /home/ol14/.ssh/known_hosts:11 Are you sure you want to continue connecting (yes/no)? yes Permission denied (publickey). |
$ssh-copy-id "ol14@192.168.0.150"
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is 02:97:d8:d2:63:62:4f:16:7e:1d:35:d3:b6:a2:a5:42. Please contact your system administrator. Add correct host key in /home/ol14/.ssh/known_hosts to get rid of this message. Offending key in /home/ol14/.ssh/known_hosts:10 RSA host key for 192.168.0.150 has changed and you have requested strict checking. Host key verification failed. |
$ssh-copy-id "ol14@192.168.0.150"
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is 02:97:d8:d2:63:62:4f:16:7e:1d:35:d3:b6:a2:a5:42. Please contact your system administrator. Add correct host key in /home/ol14/.ssh/known_hosts to get rid of this message. Offending key in /home/ol14/.ssh/known_hosts:10 RSA host key for 192.168.0.150 has changed and you have requested strict checking. Host key verification failed. |
$ssh ol14@mytest.prombez
Warning: the RSA host key for 'mytest.prombez' differs from the key for the IP address '192.168.0.150' Offending key for IP in /home/ol14/.ssh/known_hosts:10 Matching host key in /home/ol14/.ssh/known_hosts:11 Are you sure you want to continue connecting (yes/no)? yes Permission denied (publickey). |
$ssh ol14@mytest.prombez
-copy-id "ol14@192.168.0.150" @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is 02:97:d8:d2:63:62:4f:16:7e:1d:35:d3:b6:a2:a5:42. Please contact your system administrator. Add correct host key in /home/ol14/.ssh/known_hosts to get rid of this message. Offending key in /home/ol14/.ssh/known_hosts:10 RSA host key for 192.168.0.150 has changed and you have requested strict checking. Host key verification failed. |
$ssh-copy-id "ol14@192.168.0.150"
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is 02:97:d8:d2:63:62:4f:16:7e:1d:35:d3:b6:a2:a5:42. Please contact your system administrator. Add correct host key in /home/ol14/.ssh/known_hosts to get rid of this message. Offending key in /home/ol14/.ssh/known_hosts:10 RSA host key for 192.168.0.150 has changed and you have requested strict checking. Host key verification failed. |
$ssh ol14@mytest.prombez
Warning: the RSA host key for 'mytest.prombez' differs from the key for the IP address '192.168.0.150' Offending key for IP in /home/ol14/.ssh/known_hosts:10 Matching host key in /home/ol14/.ssh/known_hosts:11 Are you sure you want to continue connecting (yes/no)? yes Permission denied (publickey). |
$mc
|
$ssh ol14@mytest.prombez
Warning: the RSA host key for 'mytest.prombez' differs from the key for the IP address '192.168.0.150' Offending key for IP in /home/ol14/.ssh/known_hosts:10 Matching host key in /home/ol14/.ssh/known_hosts:11 Are you sure you want to continue connecting (yes/no)? yes ol14@mytest.prombez's password: Permission denied, please try again. ol14@mytest.prombez's password: Linux mytest 2.6.32-5-686 #1 SMP Mon Jun 13 04:13:06 UTC 2011 i686 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. You have mail. Last login: Wed Jun 29 16:09:05 2011 from adm.prombez ol14@mytest:~$ exit logout Connection to mytest.prombez closed. |
$mc
|
$ssh ol14@mytest.prombez
ol14@mytest.prombez's password: Permission denied, please try again. ol14@mytest.prombez's password: Linux mytest 2.6.32-5-686 #1 SMP Mon Jun 13 04:13:06 UTC 2011 i686 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. â/ÐзобÑÐ°Ð¶ÐµÐ½Ð¸Ñ â 4096âÐÑн 28 17:15â â/ÐÑзÑка â 4096âÐÑн 28 17:15â â/ÐбÑедоÑÑÑпнÑе â 4096âÐÑн 28 17:15â ... â â â ââ â â â ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ¤ââââââââââââââââââââââââââââââââââââ âââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ 1446M/4410M (32%) ââââââââââââââââââââââââââââââââââââââââââââââââââ root@mytest:/home/ol14# /etc/init.d/ssh restart Restarting OpenBSD Secure Shell server: sshd. root@mytest:/home/ol14# exit exit ol14@mytest:~$ exit logout Connection to mytest.prombez closed. |
Время первой команды журнала | 03:44:02 2011- 5-16 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Время последней команды журнала | 12:47:22 2011- 6-29 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Количество командных строк в журнале | 101 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Процент команд с ненулевым кодом завершения, % | 53.47 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Процент синтаксически неверно набранных команд, % | 7.92 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Суммарное время работы с терминалом *, час | 2.24 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Количество командных строк в единицу времени, команда/мин | 0.75 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Частота использования команд |
|
В журнал автоматически попадают все команды, данные в любом терминале системы.
Для того чтобы убедиться, что журнал на текущем терминале ведётся, и команды записываются, дайте команду 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