Sent: Thursday, March 21, 2019 1:47 PM
To: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] Show me all the system syslog things!
I would avoid changing "messages" since JTAC usually relies on the standard
stuff being there (and often increasing the logging to daemon any; kernel
any;). In
I would avoid changing "messages" since JTAC usually relies on the standard
stuff being there (and often increasing the logging to daemon any; kernel
any;). Instead, create a se
parate log file for your own cut-down logging.
On Thu, Mar 21, 2019 at 03:09:30PM -0400, Jason Lixfeld wrote:
> Hi,
>
{
priority-override {
severity warning;
}
}
}
}
-Original Message-
From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of
Jason Lixfeld
Sent: Thursday, March 21, 2019 12:10 PM
To: juniper-nsp
Subject: [j-nsp] Show me all the system syslog things!
H
Hi,
I’m looking for some ideas about configuring syslog.
Starting from the bare-minumum syslog config, and log-updown in BGP:
jlixfeld@lab# show system syslog
user * {
any emergency;
}
host 10.219.51.130 {
any info;
}
file messages {
any info;
}
time-format year millisecond;
The mes
4 matches
Mail list logo