Beiträge von clcclc

clcclc · 17. Oktober 2010

habe jetzt schon mal selber rausgefunden ab wann die meldung kommt sobald das sicherheitssystem jemanden auf die bannliste setzt

muß doch möglich sein die meldung abzuschalten

clcclc · 14. Oktober 2010

kann mir niemand bei diesem problem helfen

clcclc · 8. Oktober 2010

ja habe keybord und monitor direkt angeschlossen !
ab und an ist gut kommt fast alle 2 sekunden

Code

[~] # dmesg
00:1a.0: setting latency timer to 64
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000b880
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
  alloc irq_desc for 21 on node -1
  alloc kstat_irqs on node -1
uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:1a.1: setting latency timer to 64
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000b800
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.2: PCI INT D -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1a.2: setting latency timer to 64
uhci_hcd 0000:00:1a.2: UHCI Host Controller
uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1a.2: irq 19, io base 0x0000b480
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000b400
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000b080
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000b000
hub 8-0:1.0: USB hub found
hub 8-0:1.0: 2 ports detected
usb 2-1: new high speed USB device using ehci_hcd and address 2
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb: create proc systemp successfully
usb: create proc systemp successfully
Using EHCI controller.
scsi8 : usb-storage 2-1:1.0
usb 8-1: new full speed USB device using uhci_hcd and address 2
hub 8-1:1.0: USB hub found
hub 8-1:1.0: 4 ports detected
usb 8-1.1: new low speed USB device using uhci_hcd and address 3
usb 8-1.4: new full speed USB device using uhci_hcd and address 4
scsi 8:0:0:0: Direct-Access              USB DISK MODULE  PMAP PQ: 0 ANSI: 0 CCS
sd 8:0:0:0: [sdx] 1007616 512-byte logical blocks: (515 MB/492 MiB)
sd 8:0:0:0: [sdx] Write Protect is off
sd 8:0:0:0: [sdx] Mode Sense: 23 00 00 00
sd 8:0:0:0: [sdx] Assuming drive cache: write through
sd 8:0:0:0: Attached scsi generic sg23 type 0
sd 8:0:0:0: [sdx] Assuming drive cache: write through
 sdx: sdx1 sdx2 sdx3 sdx4 < sdx5 sdx6 >
sd 8:0:0:0: [sdx] Assuming drive cache: write through
sd 8:0:0:0: [sdx] Attached SCSI removable disk
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda1): mounted filesystem with writeback data mode
md: md9 stopped.
md: bind<sda1>
raid1: raid set md9 active with 1 out of 4 mirrors
md9: bitmap initialized from disk: read 5/5 pages, set 110010 bits
created bitmap (65 pages) for device md9
md9: detected capacity change from 0 to 542769152
 md9: unknown partition table
kjournald starting.  Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
md: md13 stopped.
md: bind<sda4>
raid1: raid set md13 active with 1 out of 4 mirrors
md13: bitmap initialized from disk: read 4/4 pages, set 81921 bits
created bitmap (57 pages) for device md13
md13: detected capacity change from 0 to 469893120
 md13: unknown partition table
kjournald starting.  Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
kjournald starting.  Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
kjournald starting.  Commit interval 5 seconds
EXT3-fs (md13): using internal journal
EXT3-fs (md13): mounted filesystem with writeback data mode
usbcore: registered new interface driver hiddev
input: Logitech HID compliant keyboard as /class/input/input2
generic-usb 0003:046D:C30E.0001: input: USB HID v1.10 Keyboard [Logitech HID compliant keyboard] on usb-0000:00:1d.2-1.1/input0
input: Logitech HID compliant keyboard as /class/input/input3
generic-usb 0003:046D:C30E.0002: input: USB HID v1.10 Device [Logitech HID compliant keyboard] on usb-0000:00:1d.2-1.1/input1
input: Logitech G9 Laser Mouse as /class/input/input4
generic-usb 0003:046D:C048.0003: input: USB HID v1.11 Mouse [Logitech G9 Laser Mouse] on usb-0000:00:1d.2-1.4/input0
input: Logitech G9 Laser Mouse as /class/input/input5
generic-usb 0003:046D:C048.0004: input,hiddev96: USB HID v1.11 Keyboard [Logitech G9 Laser Mouse] on usb-0000:00:1d.2-1.4/input1
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ICH7/ICH9R rtc control driver.
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
iTCO_wdt: Found a ICH9R TCO device (Version=2, TCOBASE=0x0860)
iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0)
usbcore: registered new interface driver usblp
ufsd: module license 'Commercial product' taints kernel.
Disabling lock debugging due to kernel taint
ufsd: driver head (Jul 20 2010 01:29:25) with acl LBD=OFF with ioctl loaded at f82e2000
NTFS read/write support included
Hfs+/HfsX read/write support included
kjournald starting.  Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
md: bind<sda2>
raid1: raid set md4 active with 1 out of 1 mirrors
md4: detected capacity change from 0 to 542769152
 md4: unknown partition table
Adding 530040k swap on /dev/md4.  Priority:-1 extents:1 across:530040k
active port 0 :139
active port 1 :445
active port 2 :20
EXT4-fs (sda3): mounted filesystem with ordered data mode
e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
active port 0 :139
active port 1 :445
active port 2 :20
warning: `proftpd' uses 32-bit capabilities (legacy support in use)
rule type=2, num=1
Loading iSCSI transport class v2.0-871.
iscsi: registered transport (tcp)
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1

Alles anzeigen

clcclc · 8. Oktober 2010

ich kann nix genauer beschreiben weil ich das problem genau beschrieben habe

Beispiel:

QNAPNAS Login:rule type=2, num=1
rule type=2, num=1
rule type=2, num=1

clcclc · 8. Oktober 2010

wenn ich meinen TS 439 ProII über den vga anschließe kommt dort immer die meldung
rule type=2, num=1
rule type=2, num=1
rule type=2, num=1

wenn ich login dann macht habe habe ich ja normal stilles bild ohne änderungen es sei denn ich mache eingabe
aber bei mir kommt alle paar sekunden immer wieder
rule type=2, num=1

wie kann ich das ändern das nervt wenn man da was machen möchte

Beiträge von clcclc

Komische meldung "rule type=2, num=1 "bei TS 439 ProII

Komische meldung "rule type=2, num=1 "bei TS 439 ProII

Komische meldung "rule type=2, num=1 "bei TS 439 ProII

Komische meldung "rule type=2, num=1 "bei TS 439 ProII

Komische meldung "rule type=2, num=1 "bei TS 439 ProII