remote logging with syslogd question
Victor Gamov
vit at otcnet.ru
Fri Aug 20 19:11:37 UTC 2021
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
More information about the freebsd-questions
mailing list