portato

[Pavel Kysilka]

On 28-06-2003 19.39 +0200, Marek Siwek wrote:
> Ahoj,
  zdravim,
> pouziva nekdo z vas tento program?
 pouziva ho muj kamos. mam ted od nej pujcenou masinu, tak zaslu
 konfigurak v priloze. sice do toho nevidim, ale snad to pomuze.
> Pro nezasvecene, jde o program ktery umi svitit ledkami pripojenymi na 
> paralelni port.
> Mam jednu malou otazku: jde nekomu z vas portato tak, aby svitily ledky 
> pri praci s diskem?
ano, facha to.
> portato 1.2, RH9, ledky sviti, ale dard to nechyta.
me to jede na debianu.
> Diky
> Marek
> -- 
> Marek Siwek
> marek.siwek na ei.cz
> 
 zatim
   goldenfish
------------- další část ---------------
; portato.cfg
;
; this is the configuration file for the portato program
;
; comments start with a ;
;
; blank lines are ignored
;
; you may not start comments mid-way through a line, sorry
;
; port definition must come before update rate definition must come
; before the pin definitions

;;;;;;;;;;;;;;;;;;;;;;;
; SAMPLE CONFIGURATION - tailor to suit your needs

; port section - which port to use, can be specified in ONE OF two ways
;
; port lpt <#> - use standard values for lpt port 1 or 2 (0x378 and
;                0x278 respectively)
;
; port address <0x#> - specify hexidecimal address of port to use (prefix
;                      hexidecimal number with 0x, i.e. 0x378).  please
;                      folks, know what you are doing with this option, and
;                      DON'T try random ports because you could end up
;                      hosing your entire system.  you have been warned.
;
; port <#>
port lpt 1

; update rate section - time between each poll of system (can be specified
;                       in seconds, milliseconds, or microseconds)
;
; remember of course that a lower update time means more cpu time is
; spent polling the system, but produces more accurate led output.
; values between 20 and 100 milliseconds seem reasonable on a 486-40.
; you are welcome to make it as high or as low as you wish (1 second is like
; a psychedelic christmas when system activity is sporadic, and uses very
; little CPU).  any value in the microseconds range will likely produce
; poor system performance, but i just put the option there for fun.
;
; update <#> <sec/msec/usec>
update 30 msec

; pin section - which pins get which events (note that a single pin
;               can get multiple types of activities)
;
; valid assignments:
;
; cpu <type>
;    <type> is one of:
;        "user" - user cpu activity
;        "system" - system cpu activity
;        "nice" - cpu activity by nice'd processes
;        "activity" - user, system, or nice activity
;        "idle" - cpu idle
;
; disk <drive #>
;    <drive #> is a drive number from 1-4. experiment to see which
;       number works with your drive.  probably if you have one to
;       four hard disks it's obvious which numbers correspond to which,
;       but i'm not sure if there's much more method to it than that
;       (giving a drive of 0 matches any drive activity)
;
; intr <#>
;    <#> is an interrupt number (from 1-15), this is nice for monitoring
;       serial ports, keyboards, hd/fd controllers, ethernet cards,
;       sound cards, and any other interrupt based device (you can find
;       some interrupt information about your system by typing
;       "cat /proc/interrupts").
;       typical irq numbers:
;       1 - keyboard
;       3 - COM2
;       4 - COM1
;       5 - sound card / LPT2
;       7 - sound card / LPT1
;       8-9 - reserved
;       10-12 - unassigned, often ethernet cards or sound boards
;       13 - math error
;       14 - hard drive controller
;
; net_activity <interface> - network data transmitted or received
; net_collisions <interface> - network transmission collisions
; net_receive  <interface> - network data received
; net_transmit <interface> - network data transmitted
;    <interface> is the device as it appears in field 1 of /proc/net/dev, i.e.
;       eth0, ppp1, or sl0.  note that if you specify only the first part
;       of a device then you can add multiple devices with one statement,
;       i.e. interface "eth" will get you activity for all ethernet
;       devices, and interface "ppp" will get you activity for all ppp devices
;       (make sure the device/s you specify exist in the kernel!)
;
; swap <type>
;    <type> is one of:
;        "in" - pages being brought in
;        "out" - pages being put out
;        "activity" - pages being brought in or put out
;
; pin <#> <type> <modifier>

pin 1 cpu system		; Zluta dole
;pin 2; Cervena dole
pin 3 cpu idle			; Zelena
pin 4 swap out			; Cervena vpravo
pin 5 net_transmit eth0	; Cervena dvoudioda
pin 6 net_receive eth0	; Zelena dvoudioda
pin 7 swap in			; Cervena vlevo
pin 8 intr 10			; Zluta nahore

;pin 2 					;Cervena dole
;pin 2 cpu idle			;Zelena 
;pin 3 swap out			;Cervena vpravo
;pin 4 net_transmit eth0		;Cervena dvoudioda
;pin 5 net_receive eth0		;Zelena dvoudioda
;pin 6 swap in 			;Cervena vlevo
;pin 6 intr 10			;Zluta nahore
;pin 8 cpu system ;Zluta vprostred