Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

60%
+1 −0
Q&A How do I prevent remote syslog events from printing locally?

I have a GNU/Linux host that I use to aggregate syslog events from a few switches, printers, and generally less versatile hosts on my LAN. I set up rsyslog years ago to listen on UDP:514 and save ...

1 answer  ·  posted 2y ago by re89j‭  ·  last activity 1y ago by bgstack15‭

#3: Post edited by user avatar CodeFarmer‭ · 2022-02-15T20:27:43Z (over 2 years ago)
Minor spelling fix
How do I prevent remote syslog events from printing locally?
  • I have a GNU/Linux host that I use to aggregate syslog events from a few switches, printers, and generally less versatile hosts on my LAN.
  • I set up rsyslog years ago to listen on UDP:514 and save syslog messages it receives from any host to `/var/log/netsyslog/${HostNameOrIPHere}.log` and that works.
  • ("netsyslog" was my creation)
  • LogRogate then regularly compresses them and rotates them out. It's delightful.
  • But sometimes (depending on the "severity level" probably), the remote devices' messages also interrupt me when I'm SSH'd into my linux host. (In the middle of vim is particularly annoying.)
  • How can I prevent any remote message (regardless of severity) from displaying on local login sessions?
  • Here's my current config:
  • ```
  • ==> /etc/rsyslog.conf <==
  • $ModLoad imudp
  • $UDPServerRun 514
  • $ModLoad imtcp
  • $InputTCPServerRun 514
  • $template DynaFile,"/var/log/netsyslog/%HOSTNAME%.log"
  • *.* -?DynaFile
  • $WorkDirectory /var/lib/rsyslog
  • $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
  • $IncludeConfig /etc/rsyslog.d/*.conf
  • $OmitLocalLogging on
  • $IMJournalStateFile imjournal.state
  • *.info;mail.none;authpriv.none;cron.none /var/log/messages
  • authpriv.* /var/log/secure
  • mail.* -/var/log/maillog
  • cron.* /var/log/cron
  • *.emerg :omusrmsg:*
  • uucp,news.crit /var/log/spooler
  • local7.* /var/log/boot.log
  • ```
  • ```
  • ==> /etc/rsyslog.d/listen.conf <==
  • $SystemLogSocketName /run/systemd/journal/syslog
  • ```
  • I'm thinking I want to change: `*.emerg :omusrmsg:*`
  • By adding sort of filter to it like `localhost.emerg`. But I'm not sure how to compose such a filter.
  • Maybe there's a more elegant way of doing this. I half thing perhaps I was wrong to use the same daemon to log locally-originated events as remote ones. I'm open to change.
  • I have a GNU/Linux host that I use to aggregate syslog events from a few switches, printers, and generally less versatile hosts on my LAN.
  • I set up rsyslog years ago to listen on UDP:514 and save syslog messages it receives from any host to `/var/log/netsyslog/${HostNameOrIPHere}.log` and that works.
  • ("netsyslog" was my creation)
  • LogRogate then regularly compresses them and rotates them out. It's delightful.
  • But sometimes (depending on the "severity level" probably), the remote devices' messages also interrupt me when I'm SSH'd into my linux host. (In the middle of vim is particularly annoying.)
  • How can I prevent any remote message (regardless of severity) from displaying on local login sessions?
  • Here's my current config:
  • ```
  • ==> /etc/rsyslog.conf <==
  • $ModLoad imudp
  • $UDPServerRun 514
  • $ModLoad imtcp
  • $InputTCPServerRun 514
  • $template DynaFile,"/var/log/netsyslog/%HOSTNAME%.log"
  • *.* -?DynaFile
  • $WorkDirectory /var/lib/rsyslog
  • $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
  • $IncludeConfig /etc/rsyslog.d/*.conf
  • $OmitLocalLogging on
  • $IMJournalStateFile imjournal.state
  • *.info;mail.none;authpriv.none;cron.none /var/log/messages
  • authpriv.* /var/log/secure
  • mail.* -/var/log/maillog
  • cron.* /var/log/cron
  • *.emerg :omusrmsg:*
  • uucp,news.crit /var/log/spooler
  • local7.* /var/log/boot.log
  • ```
  • ```
  • ==> /etc/rsyslog.d/listen.conf <==
  • $SystemLogSocketName /run/systemd/journal/syslog
  • ```
  • I'm thinking I want to change: `*.emerg :omusrmsg:*`
  • By adding sort of filter to it like `localhost.emerg`. But I'm not sure how to compose such a filter.
  • Maybe there's a more elegant way of doing this. I half think perhaps I was wrong to use the same daemon to log locally-originated events as remote ones. I'm open to change.
#2: Post edited by user avatar Quasímodo‭ · 2022-02-05T13:58:03Z (over 2 years ago)
Formatting
  • I have a GNU/Linux host that I use to aggregate syslog events from a few switches, printers, and generally less versatile hosts on my LAN.
  • I set up rsyslog years ago to listen on UDP:514 and save syslog messages it receives from any host to /var/log/netsyslog/${HostNameOrIPHere}.log and that works.
  • ("netsyslog" was my creation)
  • LogRogate then regularly compresses them and rotates them out. It's delightful.
  • But sometimes (depending on the "severity level" probably), the remote devices' messages also interrupt me when I'm SSH'd into my linux host. (In the middle of vim is particularly annoying.)
  • How can I prevent any remote message (regardless of severity) from displaying on local login sessions?
  • Here's my current config:
  • `[user@host ~]# grep -v -e '^$' -e '#.*$' /etc/rsyslog.* -r
  • /etc/rsyslog.conf:$ModLoad imudp
  • /etc/rsyslog.conf:$UDPServerRun 514
  • /etc/rsyslog.conf:$ModLoad imtcp
  • /etc/rsyslog.conf:$InputTCPServerRun 514
  • /etc/rsyslog.conf:$template DynaFile,"/var/log/netsyslog/%HOSTNAME%.log"
  • /etc/rsyslog.conf:*.* -?DynaFile
  • /etc/rsyslog.conf:$WorkDirectory /var/lib/rsyslog
  • /etc/rsyslog.conf:$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
  • /etc/rsyslog.conf:$IncludeConfig /etc/rsyslog.d/*.conf
  • /etc/rsyslog.conf:$OmitLocalLogging on
  • /etc/rsyslog.conf:$IMJournalStateFile imjournal.state
  • /etc/rsyslog.conf:*.info;mail.none;authpriv.none;cron.none /var/log/messages
  • /etc/rsyslog.conf:authpriv.* /var/log/secure
  • /etc/rsyslog.conf:mail.* -/var/log/maillog
  • /etc/rsyslog.conf:cron.* /var/log/cron
  • /etc/rsyslog.conf:*.emerg :omusrmsg:*
  • /etc/rsyslog.conf:uucp,news.crit /var/log/spooler
  • /etc/rsyslog.conf:local7.* /var/log/boot.log
  • /etc/rsyslog.d/listen.conf:$SystemLogSocketName /run/systemd/journal/syslog`
  • I'm thinking I want to change: *.emerg :omusrmsg:*
  • By adding sort of filter to it like localhost.emerg. But I'm not sure how to compose such a filter.
  • Maybe there's a more elegant way of doing this. I half thing perhaps I was wrong to use the same daemon to log locally-originated events as remote ones. I'm open to change.
  • I have a GNU/Linux host that I use to aggregate syslog events from a few switches, printers, and generally less versatile hosts on my LAN.
  • I set up rsyslog years ago to listen on UDP:514 and save syslog messages it receives from any host to `/var/log/netsyslog/${HostNameOrIPHere}.log` and that works.
  • ("netsyslog" was my creation)
  • LogRogate then regularly compresses them and rotates them out. It's delightful.
  • But sometimes (depending on the "severity level" probably), the remote devices' messages also interrupt me when I'm SSH'd into my linux host. (In the middle of vim is particularly annoying.)
  • How can I prevent any remote message (regardless of severity) from displaying on local login sessions?
  • Here's my current config:
  • ```
  • ==> /etc/rsyslog.conf <==
  • $ModLoad imudp
  • $UDPServerRun 514
  • $ModLoad imtcp
  • $InputTCPServerRun 514
  • $template DynaFile,"/var/log/netsyslog/%HOSTNAME%.log"
  • *.* -?DynaFile
  • $WorkDirectory /var/lib/rsyslog
  • $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
  • $IncludeConfig /etc/rsyslog.d/*.conf
  • $OmitLocalLogging on
  • $IMJournalStateFile imjournal.state
  • *.info;mail.none;authpriv.none;cron.none /var/log/messages
  • authpriv.* /var/log/secure
  • mail.* -/var/log/maillog
  • cron.* /var/log/cron
  • *.emerg :omusrmsg:*
  • uucp,news.crit /var/log/spooler
  • local7.* /var/log/boot.log
  • ```
  • ```
  • ==> /etc/rsyslog.d/listen.conf <==
  • $SystemLogSocketName /run/systemd/journal/syslog
  • ```
  • I'm thinking I want to change: `*.emerg :omusrmsg:*`
  • By adding sort of filter to it like `localhost.emerg`. But I'm not sure how to compose such a filter.
  • Maybe there's a more elegant way of doing this. I half thing perhaps I was wrong to use the same daemon to log locally-originated events as remote ones. I'm open to change.
#1: Initial revision by user avatar re89j‭ · 2022-02-04T23:18:54Z (over 2 years ago)
How do I prevent remote syslog events from printing locally?
I have a GNU/Linux host that I use to aggregate syslog events from a few switches, printers, and generally less versatile hosts on my LAN.

I set up rsyslog years ago to listen on UDP:514 and save syslog messages it receives from any host to /var/log/netsyslog/${HostNameOrIPHere}.log and that works.  
("netsyslog" was my creation)
LogRogate then regularly compresses them and rotates them out.  It's delightful.

But sometimes (depending on the "severity level" probably), the remote devices' messages also interrupt me when I'm SSH'd into my linux host.  (In the middle of vim is particularly annoying.)

How can I prevent any remote message (regardless of severity) from displaying on local login sessions?

Here's my current config:

`[user@host ~]# grep -v -e '^$' -e '#.*$' /etc/rsyslog.* -r
/etc/rsyslog.conf:$ModLoad imudp
/etc/rsyslog.conf:$UDPServerRun 514
/etc/rsyslog.conf:$ModLoad imtcp
/etc/rsyslog.conf:$InputTCPServerRun 514
/etc/rsyslog.conf:$template DynaFile,"/var/log/netsyslog/%HOSTNAME%.log"
/etc/rsyslog.conf:*.* -?DynaFile
/etc/rsyslog.conf:$WorkDirectory /var/lib/rsyslog
/etc/rsyslog.conf:$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
/etc/rsyslog.conf:$IncludeConfig /etc/rsyslog.d/*.conf
/etc/rsyslog.conf:$OmitLocalLogging on
/etc/rsyslog.conf:$IMJournalStateFile imjournal.state
/etc/rsyslog.conf:*.info;mail.none;authpriv.none;cron.none /var/log/messages
/etc/rsyslog.conf:authpriv.*      /var/log/secure
/etc/rsyslog.conf:mail.*         -/var/log/maillog
/etc/rsyslog.conf:cron.*          /var/log/cron
/etc/rsyslog.conf:*.emerg         :omusrmsg:*
/etc/rsyslog.conf:uucp,news.crit  /var/log/spooler
/etc/rsyslog.conf:local7.*        /var/log/boot.log

/etc/rsyslog.d/listen.conf:$SystemLogSocketName /run/systemd/journal/syslog`

I'm thinking I want to change: *.emerg    :omusrmsg:*
By adding sort of filter to it like localhost.emerg.  But I'm not sure how to compose such a filter.

Maybe there's a more elegant way of doing this.  I half thing perhaps I was wrong to use the same daemon to log locally-originated events as remote ones.  I'm open to change.