David,
voice style=edmcmahonYou are correct, sir!/voice
Per the inline documentation:
# if SIGHUP has arrived, reopen input files and logfile, re-read
# configuration and empty all lists concerning events and correlation
# information; *if SIGABRT has arrived, behave like SIGHUP but
Excellent points, all. I've decided to combine the two approaches.
However, I'm stuck.
As you can see below, I'm loading the hashes on startup, and the second rule
doesn't run. :( If I remove the context from the second rule, it runs fine.
I don't think context =($perl_hash{$2}) is a valid
Sorry for the double post, I wanted to post an intermediate solution:
The correct context line for the second rule would be:
context= =(if (exists $hash{GigabitEthernet1/37}) { return 1;} )
This should be the last stumbling block...
--
Justin J. Novack
Official Disturber of the Peace
On
In message
cab3_bpoyf-ppbhwvfulf2g88crcfma4q2e1fdkxxsu7moz2...@mail.gmail.com ,
Justin J. Novack writes:
Excellent points, all. I've decided to combine the two approaches.
However, I'm stuck.
As you can see below, I'm loading the hashes on startup, and the second rule
doesn't run. :( If I
Again, thank you John, David, et. al.
My full solution is posted for reference. Please feel free to include in
documentation.
/etc/sec/friendlynames.txt
GigabitEthernet1/37=TEST SERVER
GigabitEthernet3/39=IMPORTANT SERVER
/etc/sec/testing.sec
===
type=Single
On Wed, 19 Oct 2011, Justin J. Novack wrote:
Again, thank you John, David, et. al.
My full solution is posted for reference. Please feel free to include in
documentation.
/etc/sec/friendlynames.txt
GigabitEthernet1/37=TEST SERVER
GigabitEthernet3/39=IMPORTANT SERVER
Hello Everyone,
Nothing relevant has turned up in a search of the archives, so I was hoping
I could tap the collective knowledge. My dilemma is that I'd like to be
able to email out a friendly name for a port if one should exist.
Rather than writing a x number of rules for x number of ports
In message
CAB3_BpPsYVc+OKX5oio03tuSy=D=o5ikb5eq7rxtxykvuax...@mail.gmail.com ,
Justin J. Novack writes:
[...]
I could tap the collective knowledge. My dilemma is that I'd like to be
able to email out a friendly name for a port if one should exist.
Rather than writing a x number of rules for x
Great idea, however, now all 432 ports on my device would send out an email
on flap, rather than the 60 important ones. This would be perfect if an
entire switch needed friendly names.
As for David's suggestion, this would also be the case, however, I could
error out (silently) if it doesn't
On Tue, 18 Oct 2011, Justin J. Novack wrote:
Great idea, however, now all 432 ports on my device would send out an email
on flap, rather than the 60 important ones. This would be perfect if an
entire switch needed friendly names.
As for David's suggestion, this would also be the case,
10 matches
Mail list logo