Date: Fri, 20 Aug 2021 22:11:15 +0300 From: Victor Gamov <vit@otcnet.ru> To: freebsd-questions@freebsd.org Subject: Re: remote logging with syslogd question Message-ID: <7af2b86e-31a3-d6c9-5efc-446ee1851676@otcnet.ru> In-Reply-To: <a23e910c-0921-b5c4-ce18-fe42f6e63a81@kicp.uchicago.edu> References: <a23e910c-0921-b5c4-ce18-fe42f6e63a81@kicp.uchicago.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Try to use --- cut here --- #+localhost ... #-localhost --- /cut here --- for local messages and --- cut here --- #+192.168.1.1 *.* /var/log/192.168.1.1.log #-192.168.1.1 --- /cut here --- for messages from remote On 20.08.2021 18:52, Valeri Galtsev wrote: > Dear Experts, > > I decided to climb out of cave and set up remote log server. I followed > handbook to configure syslogd for that. All is trivial (spare disabling > -ss and replacing it with -s flag, as the first prevents opening network > sockets). > > But although all works like a charm, logs from remote client not only go > to designated for them place, but also are going to respective log files > of machine I use as log server. And the last makes a mess. > > I wonder if someone can think of some trivial mistake I am making. > > The only mistake I can think of is mixing two things, namely, I should > have left syslog alone to do what it does, and use separate daemon (e.g. > rsyslog) to run as remote log server. That mistake I happily admit, and > am pursuing this better avenue. But I'm still curios what obvious > mistake I might have made with syslogd. > > > Thanks for your insights! > > Valeri > -- CU, Victor Gamov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7af2b86e-31a3-d6c9-5efc-446ee1851676>