History log of /openbsd-src/usr.sbin/syslogd/Makefile (Results 1 – 9 of 9)
Revision Date Author Comments
# 2a99deb5 13-Jan-2022 martijn <martijn@openbsd.org>

Move parsing of incoming syslog messages to their own section.
This should make it more manageable.

No functional change intended, debugging output slightly changed.

help from and OK bluhm@


# bafa06e1 16-Mar-2017 bluhm <bluhm@openbsd.org>

Start to replace the home grown syslogd(8) internal debug and logging
functions with a more common log.c implementation. Of course
openlog(3) cannot be used, so adapt the log.[ch] initially copied
f

Start to replace the home grown syslogd(8) internal debug and logging
functions with a more common log.c implementation. Of course
openlog(3) cannot be used, so adapt the log.[ch] initially copied
from ospfd(8) to syslogd's special needs. As the messages are
limited to ERRBUFSIZE anyway, malloc(3) in the error logging code
can be avoided. Changing all log calls to the new API will be done
in a separate step.
OK millert@

show more ...


# b60e1f73 18-Jan-2015 bluhm <bluhm@openbsd.org>

Implement sending syslog messages over TLS.
OK reyk@


# 80dbc223 05-Oct-2014 bluhm <bluhm@openbsd.org>

Switch syslogd from using poll(2) to libevent.
test and OK nicm@; OK henning@


# c1d2012a 04-Jan-2004 djm <djm@openbsd.org>

Buffered logging for syslogd. Logs may be stored in memory buffers and
extracted using a small client. Useful for diskless systems.
much feedback from deraadt@, canacar@, jmc@, jakob@ ; ok deraadt@


# 38182445 31-Jul-2003 avsm <avsm@openbsd.org>

Privilege separated syslog daemon. The child listening to log requests drops
to user _syslogd and chroots itself, while the privileged parent grants it
access to open logfiles and other calls it nee

Privilege separated syslog daemon. The child listening to log requests drops
to user _syslogd and chroots itself, while the privileged parent grants it
access to open logfiles and other calls it needs.

The only difference from existing behaviour is that if syslog.conf changes
and syslogd receives a HUP, it will re-exec itself and have two new PIDs.
A HUP with an unchanged config will make syslogd reopen logfiles as before.

Lots of help and code from deraadt@ , and advice from millert@

Various versions tested by todd, cloder, mpech, markus, tdeval and others

show more ...


# e189ddde 21-Sep-1997 deraadt <deraadt@openbsd.org>

$OpenBSD$


# 0bab16cf 05-Jan-1996 deraadt <deraadt@openbsd.org>

sync with 4.4lite2 version, as well as netbsd changes merged by perry.
retain openbsd changes too.


# df930be7 18-Oct-1995 deraadt <deraadt@openbsd.org>

initial import of NetBSD tree