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

Содержание

Журнал

Пятница (07/31/09)

/dev/ttype
21:30:52
#vim /usr/local/etc/xinetd.conf
--- /tmp/l3-saved-8642.147.1434	2009-07-31 22:30:53.000000000 +0300
+++ /usr/local/etc/xinetd.conf	2009-07-31 22:31:26.000000000 +0300
@@ -28,10 +28,10 @@
 	# USERID logs the remote user (using RFC 1413)
 	# EXIT logs the exit status of the server.
 	# DURATION logs the duration of the session.
-	log_on_success = HOST PID
+#	log_on_success = HOST PID
 
 	# What to log when the connection fails.  Same options as above
-	log_on_failure = HOST
+#	log_on_failure = HOST
 
 	# The maximum number of connections a specific IP address can
 	# have to a specific service.  
21:30:52
#vim /usr/local/etc/xinetd.conf
--- /tmp/l3-saved-8642.12032.17710	2009-07-31 22:41:39.000000000 +0300
+++ /usr/local/etc/xinetd.conf	2009-07-31 22:42:09.000000000 +0300
@@ -28,10 +28,10 @@
 	# USERID logs the remote user (using RFC 1413)
 	# EXIT logs the exit status of the server.
 	# DURATION logs the duration of the session.
-#	log_on_success = HOST PID
+	log_on_success = HOST PID
 
 	# What to log when the connection fails.  Same options as above
-#	log_on_failure = HOST
+	log_on_failure = HOST
 
 	# The maximum number of connections a specific IP address can
 	# have to a specific service.  
@@ -44,7 +44,7 @@
 disable = no
 	socket_type = stream
 	protocol    = tcp
-	wait        = yes
+	wait        = no
 	user        = root
 	type        = INTERNAL
 	id          = time-dgram
21:30:52
#vim /usr/local/etc/xinetd.conf
--- /tmp/l3-saved-8642.12032.17710	2009-07-31 22:41:39.000000000 +0300
+++ /usr/local/etc/xinetd.conf	2009-07-31 22:42:09.000000000 +0300
@@ -28,10 +28,10 @@
 	# USERID logs the remote user (using RFC 1413)
 	# EXIT logs the exit status of the server.
 	# DURATION logs the duration of the session.
-#	log_on_success = HOST PID
+	log_on_success = HOST PID
 
 	# What to log when the connection fails.  Same options as above
-#	log_on_failure = HOST
+	log_on_failure = HOST
 
 	# The maximum number of connections a specific IP address can
 	# have to a specific service.  
@@ -44,7 +44,7 @@
 disable = no
 	socket_type = stream
 	protocol    = tcp
-	wait        = yes
+	wait        = no
 	user        = root
 	type        = INTERNAL
 	id          = time-dgram
21:31:26
#/usr/local/etc/rc.d/xinetd start
Starting xinetd.
21:31:26
#/usr/local/etc/rc.d/xinetd start
Starting xinetd.
21:31:26
#/usr/local/etc/rc.d/xinetd start
Starting xinetd.
21:31:31
#ps aux | grep xinetd

21:31:31
#ps aux | grep xinetd

21:31:31
#ps aux | grep xinetd

21:31:37
#ps wux | grep xinetd
root   10722  0,0  0,3  1676  1400  ??  Ss   22:31     0:00,00 /usr/local/sbin/xinetd -f /usr/local/etc/xinetd.conf
21:31:37
#ps wux | grep xinetd
root   10722  0,0  0,3  1676  1400  ??  Ss   22:31     0:00,00 /usr/local/sbin/xinetd -f /usr/local/etc/xinetd.conf
21:31:37
#ps wux | grep xinetd
root   10722  0,0  0,3  1676  1400  ??  Ss   22:31     0:00,00 /usr/local/sbin/xinetd -f /usr/local/etc/xinetd.conf
21:31:40
#sockstat -4l | less
21:31:40
#sockstat -4l | less
21:31:40
#sockstat -4l | less
21:31:51
#nc 192.168.16.26 19

21:31:51
#nc 192.168.16.26 19

21:31:51
#nc 192.168.16.26 19

21:31:58
#less /var/log/messages
21:31:58
#less /var/log/messages
21:31:58
#less /var/log/messages
21:32:21
#less /var/log/messages
21:32:21
#less /var/log/messages
21:32:21
#less /var/log/messages
21:32:33
#nc 192.168.16.26 19

21:32:33
#nc 192.168.16.26 19

21:32:33
#nc 192.168.16.26 19

21:33:05
#nc 192.168.16.26 19

21:33:05
#nc 192.168.16.26 19

21:33:05
#nc 192.168.16.26 19

21:33:18
#nc 192.168.16.26 19
^C
21:33:18
#nc 192.168.16.26 19
^C
21:33:18
#nc 192.168.16.26 19
^C
/dev/ttyp9
21:33:36
#tcpdump -i re0 -n port 19
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on re0, link-type EN10MB (Ethernet), capture size 96 bytes
^C
0 packets captured
2480 packets received by filter
0 packets dropped by kernel
21:33:36
#tcpdump -i re0 -n port 19
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on re0, link-type EN10MB (Ethernet), capture size 96 bytes
^C
0 packets captured
2480 packets received by filter
0 packets dropped by kernel
21:33:36
#tcpdump -i re0 -n port 19
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on re0, link-type EN10MB (Ethernet), capture size 96 bytes
^C
0 packets captured
2480 packets received by filter
0 packets dropped by kernel
/dev/ttype
21:33:52
#nc 192.168.16.26 19
^C
21:33:52
#nc 192.168.16.26 19
^C
21:33:52
#nc 192.168.16.26 19
^C
21:34:22
#tail /var/log/messages
Jul 31 22:34:24 fbsd6 xinetd[12655]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12656]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12657]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12658]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12659]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12660]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12661]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12662]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12663]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12664]: warning: can't get client address: Bad file descriptor
21:34:22
#tail /var/log/messages
Jul 31 22:34:24 fbsd6 xinetd[12655]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12656]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12657]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12658]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12659]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12660]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12661]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12662]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12663]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12664]: warning: can't get client address: Bad file descriptor
21:34:22
#tail /var/log/messages
Jul 31 22:34:24 fbsd6 xinetd[12655]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12656]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12657]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12658]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12659]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12660]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12661]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12662]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12663]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:25 fbsd6 xinetd[12664]: warning: can't get client address: Bad file descriptor
21:34:27
#tail /var/log/messages
Jul 31 22:34:29 fbsd6 xinetd[12830]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12831]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12832]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12833]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12834]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12835]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12836]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12837]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12838]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12839]: warning: can't get client address: Bad file descriptor
21:34:27
#tail /var/log/messages
Jul 31 22:34:29 fbsd6 xinetd[12830]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12831]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12832]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12833]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12834]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12835]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12836]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12837]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12838]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12839]: warning: can't get client address: Bad file descriptor
21:34:27
#tail /var/log/messages
Jul 31 22:34:29 fbsd6 xinetd[12830]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12831]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12832]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12833]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12834]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12835]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12836]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12837]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12838]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12839]: warning: can't get client address: Bad file descriptor
21:34:29
#tail /var/log/messages
Jul 31 22:34:29 fbsd6 xinetd[12996]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12997]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12998]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12999]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[13000]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:30 fbsd6 xinetd[13001]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:30 fbsd6 xinetd[13002]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:30 fbsd6 xinetd[13003]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:30 fbsd6 xinetd[13004]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:30 fbsd6 xinetd[13005]: warning: can't get client address: Bad file descriptor
21:34:29
#tail /var/log/messages
Jul 31 22:34:29 fbsd6 xinetd[12996]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12997]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12998]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12999]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[13000]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:30 fbsd6 xinetd[13001]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:30 fbsd6 xinetd[13002]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:30 fbsd6 xinetd[13003]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:30 fbsd6 xinetd[13004]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:30 fbsd6 xinetd[13005]: warning: can't get client address: Bad file descriptor
21:34:29
#tail /var/log/messages
Jul 31 22:34:29 fbsd6 xinetd[12996]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12997]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12998]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[12999]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:29 fbsd6 xinetd[13000]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:30 fbsd6 xinetd[13001]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:30 fbsd6 xinetd[13002]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:30 fbsd6 xinetd[13003]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:30 fbsd6 xinetd[13004]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:30 fbsd6 xinetd[13005]: warning: can't get client address: Bad file descriptor
21:34:30
#tail /var/log/messages
Jul 31 22:34:31 fbsd6 xinetd[13254]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13255]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13256]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13257]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13258]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13259]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13260]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13261]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13262]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13263]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13265]: warning: can't get client address: Bad file descriptor
21:34:30
#tail /var/log/messages
Jul 31 22:34:31 fbsd6 xinetd[13254]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13255]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13256]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13257]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13258]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13259]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13260]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13261]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13262]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13263]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13265]: warning: can't get client address: Bad file descriptor
21:34:30
#tail /var/log/messages
Jul 31 22:34:31 fbsd6 xinetd[13254]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13255]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13256]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13257]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13258]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13259]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13260]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13261]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13262]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13263]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:31 fbsd6 xinetd[13265]: warning: can't get client address: Bad file descriptor
21:34:31
#tail /var/log/messages
Jul 31 22:34:32 fbsd6 xinetd[13602]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13603]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13604]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13605]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13606]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13607]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13608]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13609]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13610]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13611]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13613]: warning: can't get client address: Bad file descriptor
21:34:31
#tail /var/log/messages
Jul 31 22:34:32 fbsd6 xinetd[13602]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13603]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13604]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13605]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13606]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13607]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13608]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13609]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13610]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13611]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13613]: warning: can't get client address: Bad file descriptor
21:34:31
#tail /var/log/messages
Jul 31 22:34:32 fbsd6 xinetd[13602]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13603]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13604]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13605]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13606]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13607]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13608]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13609]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13610]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13611]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:32 fbsd6 xinetd[13613]: warning: can't get client address: Bad file descriptor
21:34:32
#/usr/local/etc/rc.d/xinetd reart
Stopping xinetd.
Waiting for PIDS: 10722.
Starting xinetd.
21:34:32
#/usr/local/etc/rc.d/xinetd reart
Stopping xinetd.
Waiting for PIDS: 10722.
Starting xinetd.
21:34:32
#/usr/local/etc/rc.d/xinetd reart
Stopping xinetd.
Waiting for PIDS: 10722.
Starting xinetd.
21:34:42
#tail /var/log/messages
Jul 31 22:34:35 fbsd6 xinetd[14566]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[14567]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[14568]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[14569]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[14570]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[14571]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[10722]: Deactivating service chargen due to excessive incoming connections.  Restarting in 10 seconds.
Jul 31 22:34:39 fbsd6 xinetd[10722]: Exiting...
Jul 31 22:34:43 fbsd6 xinetd[14593]: xinetd Version 2.3.14 started with libwrap loadavg options compiled in.
Jul 31 22:34:43 fbsd6 xinetd[14593]: Started working: 2 available services
21:34:42
#tail /var/log/messages
Jul 31 22:34:35 fbsd6 xinetd[14566]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[14567]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[14568]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[14569]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[14570]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[14571]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[10722]: Deactivating service chargen due to excessive incoming connections.  Restarting in 10 seconds.
Jul 31 22:34:39 fbsd6 xinetd[10722]: Exiting...
Jul 31 22:34:43 fbsd6 xinetd[14593]: xinetd Version 2.3.14 started with libwrap loadavg options compiled in.
Jul 31 22:34:43 fbsd6 xinetd[14593]: Started working: 2 available services
21:34:42
#tail /var/log/messages
Jul 31 22:34:35 fbsd6 xinetd[14566]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[14567]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[14568]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[14569]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[14570]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[14571]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:35 fbsd6 xinetd[10722]: Deactivating service chargen due to excessive incoming connections.  Restarting in 10 seconds.
Jul 31 22:34:39 fbsd6 xinetd[10722]: Exiting...
Jul 31 22:34:43 fbsd6 xinetd[14593]: xinetd Version 2.3.14 started with libwrap loadavg options compiled in.
Jul 31 22:34:43 fbsd6 xinetd[14593]: Started working: 2 available services
21:34:46
#nc 192.168.16.26 19

21:34:46
#nc 192.168.16.26 19

21:34:46
#nc 192.168.16.26 19

21:34:53
#sockstat -4l | less
21:34:53
#sockstat -4l | less
21:34:53
#sockstat -4l | less
21:35:15
#tail /var/log/messages
Jul 31 22:34:53 fbsd6 xinetd[14652]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14653]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14654]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14655]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14656]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14657]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14658]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14659]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14593]: Deactivating service chargen due to excessive incoming connections.  Restarting in 10 seconds.
Jul 31 22:35:11 fbsd6 xinetd[14593]: Activating service chargen
21:35:15
#tail /var/log/messages
Jul 31 22:34:53 fbsd6 xinetd[14652]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14653]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14654]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14655]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14656]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14657]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14658]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14659]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14593]: Deactivating service chargen due to excessive incoming connections.  Restarting in 10 seconds.
Jul 31 22:35:11 fbsd6 xinetd[14593]: Activating service chargen
21:35:15
#tail /var/log/messages
Jul 31 22:34:53 fbsd6 xinetd[14652]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14653]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14654]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14655]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14656]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14657]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14658]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14659]: warning: can't get client address: Bad file descriptor
Jul 31 22:34:53 fbsd6 xinetd[14593]: Deactivating service chargen due to excessive incoming connections.  Restarting in 10 seconds.
Jul 31 22:35:11 fbsd6 xinetd[14593]: Activating service chargen
21:35:17
#sockstat -4l | less
21:35:17
#sockstat -4l | less
21:35:17
#sockstat -4l | less
21:35:21
#nc 192.168.16.26 19

21:35:21
#nc 192.168.16.26 19

21:35:21
#nc 192.168.16.26 19

21:35:36
#tail /var/log/messages
Jul 31 22:35:36 fbsd6 xinetd[16832]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[16833]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[16834]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[16835]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[16836]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[16837]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[14593]: Deactivating service chargen due to excessive incoming connections.  Restarting in 10 seconds.
Jul 31 22:35:42 fbsd6 kernel: re0: promiscuous mode disabled
Jul 31 22:35:54 fbsd6 xinetd[14593]: Activating service chargen
Jul 31 22:35:58 fbsd6 kernel: lo0: promiscuous mode enabled
21:35:36
#tail /var/log/messages
Jul 31 22:35:36 fbsd6 xinetd[16832]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[16833]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[16834]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[16835]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[16836]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[16837]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[14593]: Deactivating service chargen due to excessive incoming connections.  Restarting in 10 seconds.
Jul 31 22:35:42 fbsd6 kernel: re0: promiscuous mode disabled
Jul 31 22:35:54 fbsd6 xinetd[14593]: Activating service chargen
Jul 31 22:35:58 fbsd6 kernel: lo0: promiscuous mode enabled
21:35:36
#tail /var/log/messages
Jul 31 22:35:36 fbsd6 xinetd[16832]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[16833]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[16834]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[16835]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[16836]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[16837]: warning: can't get client address: Bad file descriptor
Jul 31 22:35:36 fbsd6 xinetd[14593]: Deactivating service chargen due to excessive incoming connections.  Restarting in 10 seconds.
Jul 31 22:35:42 fbsd6 kernel: re0: promiscuous mode disabled
Jul 31 22:35:54 fbsd6 xinetd[14593]: Activating service chargen
Jul 31 22:35:58 fbsd6 kernel: lo0: promiscuous mode enabled
/dev/ttyp9
21:35:42
#tcpdump -i lon port 19
tcpdump: BIOCSETIF: lo: Device not configured
21:35:42
#tcpdump -i lon port 19
tcpdump: BIOCSETIF: lo: Device not configured
21:35:42
#tcpdump -i lon port 19
tcpdump: BIOCSETIF: lo: Device not configured
21:35:48
#ifconfig
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
        inet 192.168.16.26 netmask 0xffffff00 broadcast 192.168.16.255
        ether 00:16:4e:00:00:06
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
re1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
        inet 192.168.54.158 netmask 0xffffffe0 broadcast 192.168.54.159
        ether 00:16:4e:00:01:06
...
re2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
        ether 00:16:4e:00:02:06
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
        inet6 ::1 prefixlen 128
        inet 127.0.0.1 netmask 0xff000000
21:35:48
#ifconfig
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
        inet 192.168.16.26 netmask 0xffffff00 broadcast 192.168.16.255
        ether 00:16:4e:00:00:06
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
re1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
        inet 192.168.54.158 netmask 0xffffffe0 broadcast 192.168.54.159
        ether 00:16:4e:00:01:06
...
re2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
        ether 00:16:4e:00:02:06
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
        inet6 ::1 prefixlen 128
        inet 127.0.0.1 netmask 0xff000000
21:35:48
#ifconfig
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
        inet 192.168.16.26 netmask 0xffffff00 broadcast 192.168.16.255
        ether 00:16:4e:00:00:06
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
re1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
        inet 192.168.54.158 netmask 0xffffffe0 broadcast 192.168.54.159
        ether 00:16:4e:00:01:06
...
re2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
        ether 00:16:4e:00:02:06
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
        inet6 ::1 prefixlen 128
        inet 127.0.0.1 netmask 0xff000000
/dev/ttype
21:36:02
#sockstat -4l | less
21:36:02
#sockstat -4l | less
21:36:02
#sockstat -4l | less
21:36:06
#nc 192.168.16.26 19

21:36:06
#nc 192.168.16.26 19

21:36:06
#nc 192.168.16.26 19

21:36:09
#tail /var/log/messages
Jul 31 22:36:09 fbsd6 xinetd[16929]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16930]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16931]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16932]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16933]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16934]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16935]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16936]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[14593]: Deactivating service chargen due to excessive incoming connections.  Restarting in 10 seconds.
Jul 31 22:36:27 fbsd6 xinetd[14593]: Activating service chargen
21:36:09
#tail /var/log/messages
Jul 31 22:36:09 fbsd6 xinetd[16929]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16930]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16931]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16932]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16933]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16934]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16935]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16936]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[14593]: Deactivating service chargen due to excessive incoming connections.  Restarting in 10 seconds.
Jul 31 22:36:27 fbsd6 xinetd[14593]: Activating service chargen
21:36:09
#tail /var/log/messages
Jul 31 22:36:09 fbsd6 xinetd[16929]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16930]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16931]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16932]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16933]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16934]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16935]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[16936]: warning: can't get client address: Bad file descriptor
Jul 31 22:36:09 fbsd6 xinetd[14593]: Deactivating service chargen due to excessive incoming connections.  Restarting in 10 seconds.
Jul 31 22:36:27 fbsd6 xinetd[14593]: Activating service chargen
21:36:34
#df -h
Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/ad0s1a    1.9G     66M    1.7G     4%    /
devfs          1.0K    1.0K      0B   100%    /dev
/dev/ad0s2e    496M    120K    456M     0%    /tmp
/dev/ad0s2f    3.4G    2.7G    511M    84%    /usr
/dev/ad0s2d    1.9G     42M    1.7G     2%    /var
21:36:34
#df -h
Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/ad0s1a    1.9G     66M    1.7G     4%    /
devfs          1.0K    1.0K      0B   100%    /dev
/dev/ad0s2e    496M    120K    456M     0%    /tmp
/dev/ad0s2f    3.4G    2.7G    511M    84%    /usr
/dev/ad0s2d    1.9G     42M    1.7G     2%    /var
21:36:34
#df -h
Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/ad0s1a    1.9G     66M    1.7G     4%    /
devfs          1.0K    1.0K      0B   100%    /dev
/dev/ad0s2e    496M    120K    456M     0%    /tmp
/dev/ad0s2f    3.4G    2.7G    511M    84%    /usr
/dev/ad0s2d    1.9G     42M    1.7G     2%    /var
21:39:22
#vim /usr/local/etc/xinetd.conf
--- /tmp/l3-saved-8642.12032.17710	2009-07-31 22:41:39.000000000 +0300
+++ /usr/local/etc/xinetd.conf	2009-07-31 22:42:09.000000000 +0300
@@ -28,10 +28,10 @@
 	# USERID logs the remote user (using RFC 1413)
 	# EXIT logs the exit status of the server.
 	# DURATION logs the duration of the session.
-#	log_on_success = HOST PID
+	log_on_success = HOST PID
 
 	# What to log when the connection fails.  Same options as above
-#	log_on_failure = HOST
+	log_on_failure = HOST
 
 	# The maximum number of connections a specific IP address can
 	# have to a specific service.  
@@ -44,7 +44,7 @@
 disable = no
 	socket_type = stream
 	protocol    = tcp
-	wait        = yes
+	wait        = no
 	user        = root
 	type        = INTERNAL
 	id          = time-dgram
21:39:22
#vim /usr/local/etc/xinetd.conf
--- /tmp/l3-saved-8642.6199.5049	2009-07-31 22:42:40.000000000 +0300
+++ /usr/local/etc/xinetd.conf	2009-07-31 22:42:51.000000000 +0300
@@ -44,7 +44,7 @@
 disable = no
 	socket_type = stream
 	protocol    = tcp
-	wait        = no
+	wait        = yes
 	user        = root
 	type        = INTERNAL
 	id          = time-dgram
21:39:22
#vim /usr/local/etc/xinetd.conf
--- /tmp/l3-saved-8642.6199.5049	2009-07-31 22:42:40.000000000 +0300
+++ /usr/local/etc/xinetd.conf	2009-07-31 22:42:51.000000000 +0300
@@ -44,7 +44,7 @@
 disable = no
 	socket_type = stream
 	protocol    = tcp
-	wait        = no
+	wait        = yes
 	user        = root
 	type        = INTERNAL
 	id          = time-dgram
21:42:09
#/usr/local/etc/rc.d/xinetd restart
Stopping xinetd.
Starting xinetd.
21:42:09
#/usr/local/etc/rc.d/xinetd restart
Stopping xinetd.
Starting xinetd.

Статистика

Время первой команды журнала21:30:52 2009- 7-31
Время последней команды журнала21:42:09 2009- 7-31
Количество командных строк в журнале101
Процент команд с ненулевым кодом завершения, %17.82
Процент синтаксически неверно набранных команд, % 0.00
Суммарное время работы с терминалом *, час 0.19
Количество командных строк в единицу времени, команда/мин 8.95
Частота использования команд
tail27|======================| 22.69%
nc24|====================| 20.17%
less18|===============| 15.13%
sockstat12|==========| 10.08%
/usr/local/etc/rc.d/xinetd8|======| 6.72%
ps6|=====| 5.04%
grep6|=====| 5.04%
tcpdump6|=====| 5.04%
vim6|=====| 5.04%
ifconfig3|==| 2.52%
df3|==| 2.52%
____
*) Интервалы неактивности длительностью 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$