OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
VE4KLM > JNOS     20.04.20 22:03l 44 Lines 1396 Bytes #-1825 (0) @ WW
BID : K4UVE4KLMIL]
Read: DF7EAV DJ6UX GUEST
Subj: jnos 2.0 log triggers
Path: DB0FHN<DB0PM<OE2XZR<OE5XBR<OE1XAB<HG8LXL<CX2SA<N3HYM<GB7CIP<VE4KLM
Sent: 200420/2329z @:VE4KLM.#WPG.MB.CAN.NOAM [Winnipeg] #:49307 $:K4UVE4KLMil]

This is powerful I think, hopefully you guys like this :)

Thanks Charles (N2NOV) for the great idea, really I like this !

  wget "https://www.langelaar.net/jnos2/downloads/main.log_triggers.c" --no-check-certificate

  replace your main.c with this new main.log_triggers.c, then run 'make'

Autoexec.nos examples (the sky is the limit actually) :

  # 18Apr2020, Maiko (VE4KLM), NEW log (action) triggers

  log trigger "fwd failed&" "mailmsg ve4klm fwd failed has been noted"
  log trigger "lzhuf&error&" "mailmsg ve4klm lzhuf protocol error ?"
  log trigger "adding mbox|" "sh ./adding.sh"

  log timer 300

Usage example :

 jnos> log
 Usage: log file [ nos.log | daily ] THEN log [ on | off]
        disk logging is ON, logfile type is DDMMMYY (daily)

 prototype (Apr2020) JNOS 2.0 log triggers (not final)

        log trigger "a&b c&" | "a|b c|"
        log timer [seconds]     this is trigger queue timer
 jnos> log timer
 log trigger timer = 163/300

There is NO documentation, this stuff will change, no need to give
suggestions right now, just try it out if this looks useful to you,
you can specify spaces in your trigger patterns. Being it's a prototype,
it's either ALL & (AND) or ALL | (OR), you can't mix right now. obviously
if there is only onestring (then you can use either & or |), have fun
figuring it out.

Now heading out on the road for a bit :)

Maiko / VE4KLM /ex




Read previous mail | Read next mail


 22.04.2025 12:37:28lGo back Go up