> The main issue with remote logging is that your log messages could be
> lost when destination is unreachable.
I'll have a look into it. Using only base would be pleasant, but it's
definitely not mandatory. As my project hasn't reached implementation
I'll begin my evaluation on the drawing board t
he...@ezaquarii.com writes:
> On 2021-04-24 22:50, li...@mailbox.org wrote:
> > Do you have any best / bad practices at hand regarding OpenBSD and
> > optionally the syslogd / tools it ships with?
>
> The main issue with remote logging is that your log messages could be
> lost
> when destination i
On 2021-04-24 22:50, li...@mailbox.org wrote:
Do you have any best / bad practices at hand regarding OpenBSD and
optionally the syslogd / tools it ships with?
The main issue with remote logging is that your log messages could be
lost
when destination is unreachable.
Default syslogd(8) shippe
Good evening folks and sorry if I may am unintentionally generating noise on
this list. This is my first attempt, so I hope everything is going well and
according to plan.
After setting up my first OpenBSD server the question arose as to what could be
a good setup for a centralized log manageme
>Do you have any best / bad practices at hand regarding OpenBSD and optionally
>the syslogd / tools it ships with?
Take a look at /etc/syslog.conf and syslog.conf(5). You said you have to deal
with logs on several machines? The syslog utility can direct log messages to
other machines; /etc/syslo
5 matches
Mail list logo
