tron@tron-htpc-server:~$ dpkg -L tcl8.6-dev tcl8.6 | nc -q 2 -w 2
This is nc from the netcat-openbsd package. An alternative nc is available
in the netcat-traditional package.
usage: nc [-46bCDdhjklnrStUuvZz] [-I length] [-i interval] [-O length]
	  [-P proxy_username] [-p source_port] [-q seconds] [-s source]
	  [-T toskeyword] [-V rtable] [-w timeout] [-X proxy_protocol]
	  [-x proxy_address[:port]] [destination] [port]
tron@tron-htpc-server:~$
Es ist ein Fehler aufgetreten.

Die neue PIN kann nicht akzeptiert werden. Bitte erdenken Sie eine andere PIN. Die TAN ist damit nicht mehr nutzbar.

Freundliche Grüße

Sparkasse
Tipps
Ihre PIN muss 5 Zeichen umfassen, welche aus Ziffern und Buchstaben (auch Umlauten) bestehen können. Bitte verzichten Sie jedoch auf Leer- und Sonderzeichen, sowie leicht zu erratende Zeichenfolgen (wie z.B. 12345, Tastaturkürzel oder Ihr Geburtsdatum). Desweiteren verwenden Sie bitte keine bereits von Ihnen genutzte PIN.
public boolean onInterceptTouchEvent(MotionEvent ev) {
		if (scaleDetector != null) {
			scaleDetector.onTouchEvent(ev);
			if (scaleDetector.isInProgress()) {
				return false;
			} else {
				return false;
			}
		}
		return false;
	}
server {
                listen       80; 
                server_name  herz.pw www.herz.pw;
                index           index.html;
                root         /home/andi/temp/;
        }
ego@devapp03:~$ /sbin/ethtool -k eth0
Offload parameters for eth0:
Cannot get device GRO settings: Operation not permitted
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp-segmentation-offload: on
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: off
large-receive-offload: off
ntuple-filters: off
receive-hashing: off
ego@devapp03:~$ /sbin/ethtool eth0
Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   1000baseT/Full 
                                10000baseT/Full 
        Supports auto-negotiation: No
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Speed: 10000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        MDI-X: Unknown
Cannot get wake-on-lan settings: Operation not permitted
Cannot get link status: Operation not permitted
%YAML 1.1
---

# Suricata configuration file. In addition to the comments describing all
# options in this file, full documentation can be found at:
# https://redmine.openinfosecfoundation.org/projects/suricata/wiki/Suricatayaml


# Number of packets allowed to be processed simultaneously.  Default is a
# conservative 1024. A higher number will make sure CPU's/CPU cores will be
# more easily kept busy, but may negatively impact caching.
#
# If you are using the CUDA pattern matcher (mpm-algo: ac-cuda), different rules
# apply. In that case try something like 60000 or more. This is because the CUDA
# pattern matcher buffers and scans as many packets as possible in parallel.
#max-pending-packets: 1024

# Runmode the engine should use. Please check --list-runmodes to get the available
# runmodes for each packet acquisition method. Defaults to "autofp" (auto flow pinned
# load balancing).
#runmode: autofp

# Specifies the kind of flow load balancer used by the flow pinned autofp mode.
#
# Supported schedulers are:
#
# round-robin       - Flows assigned to threads in a round robin fashion.
# active-packets    - Flows assigned to threads that have the lowest number of
#                     unprocessed packets (default).
# hash              - Flow alloted usihng the address hash. More of a random
%YAML 1.1
---

# Suricata configuration file. In addition to the comments describing all
# options in this file, full documentation can be found at:
# https://redmine.openinfosecfoundation.org/projects/suricata/wiki/Suricatayaml


# Number of packets allowed to be processed simultaneously.  Default is a
# conservative 1024. A higher number will make sure CPU's/CPU cores will be
# more easily kept busy, but may negatively impact caching.
#
# If you are using the CUDA pattern matcher (mpm-algo: ac-cuda), different rules
# apply. In that case try something like 60000 or more. This is because the CUDA
# pattern matcher buffers and scans as many packets as possible in parallel.
#max-pending-packets: 1024

# Runmode the engine should use. Please check --list-runmodes to get the available
# runmodes for each packet acquisition method. Defaults to "autofp" (auto flow pinned
# load balancing).
#runmode: autofp

# Specifies the kind of flow load balancer used by the flow pinned autofp mode.
#
# Supported schedulers are:
#
# round-robin       - Flows assigned to threads in a round robin fashion.
# active-packets    - Flows assigned to threads that have the lowest number of
#                     unprocessed packets (default).
# hash              - Flow alloted usihng the address hash. More of a random
[pid 19798] munmap(0xb48d7000, 4096)    = 0
[pid 19798] socket(PF_PACKET, SOCK_RAW, 768) = 7
[pid 19798] ioctl(7, SIOCGIFINDEX, {ifr_name="lo", ifr_index=1}) = 0
[pid 19798] ioctl(7, SIOCGIFHWADDR, {ifr_name="eth0", ifr_hwaddr=00:50:56:a2:66:3b}) = 0
[pid 19798] ioctl(7, SIOCGIFINDEX, {ifr_name="eth0", ifr_index=4}) = 0
[pid 19798] bind(7, {sa_family=AF_PACKET, proto=0x03, if4, pkttype=PACKET_HOST, addr(0)={0, }, 20 <unfinished ...>
[pid 19797] <... nanosleep resumed> NULL) = 0
[pid 19797] nanosleep({0, 100000}, NULL) = 0
[pid 19797] nanosleep({0, 100000},  <unfinished ...>
[pid 19798] <... bind resumed> )        = 0
[pid 19798] getsockopt(7, SOL_SOCKET, SO_ERROR <unfinished ...>
[pid 19797] <... nanosleep resumed> NULL) = 0
[pid 19798] <... getsockopt resumed> , [0], [4]) = 0
[pid 19797] nanosleep({0, 100000},  <unfinished ...>
[pid 19798] setsockopt(7, SOL_PACKET, PACKET_ADD_MEMBERSHIP, "\4\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 16) = 0
[pid 19798] setsockopt(7, SOL_PACKET, 0x8 /* PACKET_??? */, [1], 4) = 0
[pid 19798] getsockopt(7, SOL_PACKET, 0xb /* PACKET_??? */, [28], [4]) = 0
[pid 19798] setsockopt(7, SOL_PACKET, 0xa /* PACKET_??? */, [1], 4) = 0
[pid 19798] setsockopt(7, SOL_PACKET, 0xc /* PACKET_??? */, [4], 4) = 0
[pid 19798] setsockopt(7, SOL_PACKET, PACKET_RX_RING, "\0\20\0\0\234\2\0\0 \6\0\0008\5\0\0", 16 <unfinished ...>
[pid 19797] <... nanosleep resumed> NULL) = 0
[pid 19797] nanosleep({0, 100000}, NULL) = 0
[pid 19797] nanosleep({0, 100000},  <unfinished ...>
[pid 19798] <... setsockopt resumed> )  = 0
[pid 19798] mmap2(NULL, 2736128, PROT_READ|PROT_WRITE, MAP_SHARED, 7, 0) = 0xb4464000
[pid 19798] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 8
[pid 19798] ioctl(8, SIOCETHTOOL, 0xb50d607c) = -1 EPERM (Operation not permitted)
[pid 19798] gettimeofday({1396012736, 986289}, NULL) = 0
[pid 19798] write(1, "28/3/2014 -- 14:18:56 - <Warning"..., 14228/3/2014 -- 14:18:56 - <Warning> - [ERRCODE: SC_ERR_SYSCALL(50)] - Failure when trying to get f
eature via ioctl: Operation not permitted (1)
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-60-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     Hitachi HDS721010DLE630
Serial Number:    MSE5215V085L7L
LU WWN Device Id: 5 000cca 37cc3b7f2
Firmware Version: MS2OA5Q0
User Capacity:    1.000.204.886.016 bytes [1,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Sat Mar 29 12:43:51 2014 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x84) Offline data collection activity
                                        was suspended by an interrupting command from host.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                ( 7313) seconds.
Offline data collection