History log of /src/usr.sbin/syslogd/syslog.conf (Results 1 – 25 of 38)
Revision Date Author Comments
# d0b2dbfa 16-Aug-2023 Warner Losh <imp@FreeBSD.org>

Remove $FreeBSD$: one-line sh pattern

Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/


# cd4b2a3c 17-Sep-2019 Steve Wills <swills@FreeBSD.org>

log daemon.info to /var/log/daemon.log by default

log daemon facility now that daemon(8) has syslog support which defaults to
daemon facility, info priority

Reviewed by: bapt
Approved by: bapt
Di

log daemon.info to /var/log/daemon.log by default

log daemon facility now that daemon(8) has syslog support which defaults to
daemon facility, info priority

Reviewed by: bapt
Approved by: bapt
Differential Revision: https://reviews.freebsd.org/D21561

show more ...


# 64be79ef 21-Aug-2018 Brad Davis <brd@FreeBSD.org>

Move all syslogd related configs to usr.sbin/syslogd/

This helps with pkgbase as it switches these to use CONFS which properly tags
them as config files.

Approved by: will (mentor)
Differential Rev

Move all syslogd related configs to usr.sbin/syslogd/

This helps with pkgbase as it switches these to use CONFS which properly tags
them as config files.

Approved by: will (mentor)
Differential Revision: https://reviews.freebsd.org/D16783

show more ...


# e5c4c8aa 13-May-2017 Enji Cooper <ngie@FreeBSD.org>

Handle the logfiles in newsyslog and syslogd conditionally, based on
src.conf(5) knobs

This will allow consumers of FreeBSD to use the unmodified configuration
files out of the box more than previou

Handle the logfiles in newsyslog and syslogd conditionally, based on
src.conf(5) knobs

This will allow consumers of FreeBSD to use the unmodified configuration
files out of the box more than previously.

Both newsyslog.conf and syslog.conf:
- /var/log/lpd-errs (MK_LPR != no)
- /var/log/ppp.log (MK_PPP != no)
- /var/log/xferlog (MK_FTP != no)

newsyslog.conf:
- /var/log/amd.log (MK_AMD != no)
- /var/log/pflog (MK_PF != no)
- /var/log/sendmail.st (MK_SENDMAIL != no)

MFC after: 3 weeks
Sponsored by: Dell EMC Isilon

show more ...


# fdec22c3 01-Nov-2016 Baptiste Daroussin <bapt@FreeBSD.org>

syslogd(8): add an 'include' keyword

All the '.conf' files not beginning with a '.' contained int he directory
following the keyword will be included.

This keyword can only be used in the first lev

syslogd(8): add an 'include' keyword

All the '.conf' files not beginning with a '.' contained int he directory
following the keyword will be included.

This keyword can only be used in the first level configuration files.

Modify the default syslogd.conf to 'include' /etc/syslog.d and
/usr/local/etc/syslog.d

It simplify a lot handling of syslog from automation tools.

Reviewed by: markj, kib (via irc)
Approved by: markj
MFC after: 2 weeks
Relnotes: yes
Differential Revision: https://reviews.freebsd.org/D8402

show more ...


# f0038a8e 13-Dec-2013 Alan Somers <asomers@FreeBSD.org>

sbin/devd/devd.cc
Promoting the SIGINFO handler's log message from LOG_INFO to
LOG_NOTICE, and promoting the "Processing event ..." message from
LOG_DEBUG to LOG_INFO. Setting the logfile to LOG_

sbin/devd/devd.cc
Promoting the SIGINFO handler's log message from LOG_INFO to
LOG_NOTICE, and promoting the "Processing event ..." message from
LOG_DEBUG to LOG_INFO. Setting the logfile to LOG_NOTICE with this
change will have the same result as setting it to LOG_INFO without
this change. Setting it to LOG_INFO with this change will include
the useful "Processing event ..." messages that were previously at
LOG_DEBUG, without including useless messages like "Pushing table".

The intent of this change is that one can log "Processing event ..."
without logging "Pushing table" and related messages that are sent
for every event. The number of lines actually logged is reduced by
about 75% by making this change and setting syslog to LOG_INFO vs
setting syslog to LOG_DEBUG.

etc/syslog.conf
Changing the recommended loglevel to notice instead of info.

Sponsored by: Spectra Logic Corp
MFC after: 4 weeks

show more ...


# 6d1014a3 01-Jul-2013 Alan Somers <asomers@FreeBSD.org>

Add syslog(3) support to devd(8).

sbin/devd/devd.cc
All output will now go to syslog(3) if devd is daemonized, or stderr
if it's running in the foreground.

sbin/devd/devd.8

Add syslog(3) support to devd(8).

sbin/devd/devd.cc
All output will now go to syslog(3) if devd is daemonized, or stderr
if it's running in the foreground.

sbin/devd/devd.8
Remove the "-D" flag. Filtering messages by priority now
happens in the usual syslog way. For performance reasons, a few
extra-verbose debugging statements are now conditional on the "-d" (do
not daemonize) flag.

etc/syslog.conf
etc/newsyslog.conf
Direct messages from devd(8) to /var/log/devd.log, but leave it
disabled by default

Reviewed by: eadler
Approved by: gibbs (co-mentor)
MFC after: never (removed a command-line option from devd)

show more ...


# e19c9e1e 01-Jul-2012 Christian Brueffer <brueffer@FreeBSD.org>

Similar to all.log, mention that /var/log/console.log has to be created and chmod'ed
to make logging work.

PR: 168889
Submitted by: Robert Simmons <rsimmons0@gmail.com>
MFC after: 1 week


# 44672a29 11-Jun-2009 Andriy Gapon <avg@FreeBSD.org>

syslog.conf: pop up from logging only ppp messages at the end of file

This allows to append custom rules at the end of the file without
risk of confusion that can result when one misses default !ppp

syslog.conf: pop up from logging only ppp messages at the end of file

This allows to append custom rules at the end of the file without
risk of confusion that can result when one misses default !ppp line
and doesn't add another program specification and thus subsequent
selector(s) would belong to ppp program block.

Requested by: marck
Submitted by: marck
Approved by: jhb (mentor)

show more ...


# dcaf4eb3 02-Dec-2008 Ken Smith <kensmith@FreeBSD.org>

Remove slip.log. Slip got removed as part of the MPSAFE tty work. If
it does come back it would probably be better if users who were interested
in slip added appropriate lines instead of this being

Remove slip.log. Slip got removed as part of the MPSAFE tty work. If
it does come back it would probably be better if users who were interested
in slip added appropriate lines instead of this being here unconditionally.

Reminded by: tut <at> nhamon <dot> com <dot> ua

show more ...


# 90919545 12-Mar-2005 Gleb Smirnoff <glebius@FreeBSD.org>

Fix a terrible braino in last commit. Put kern.debug back to /var/log/messages
and do exactly what last commit message described.


# bcdbb13a 22-Feb-2005 Gleb Smirnoff <glebius@FreeBSD.org>

Do not print kernel debugging on console. In case of serial console
this can cause a really heavy load on system. Several kernel debugging
messages can be triggered even remotely (e.g. bad ARP replie

Do not print kernel debugging on console. In case of serial console
this can cause a really heavy load on system. Several kernel debugging
messages can be triggered even remotely (e.g. bad ARP replies).

Use kern.warning instead, so that really significant messages still
will be printed on console.

Reviewed by: current@
MFC after: 1 week
Security: this change fixes a DoS condition, when default system
console is serial, and box is flooded with bogus ARP
packets

show more ...


# 5b9cb0c3 23-Apr-2003 Dag-Erling Smørgrav <des@FreeBSD.org>

Make sure debug.log only gets debugging messages.


# 4845d27e 08-Apr-2003 Dag-Erling Smørgrav <des@FreeBSD.org>

Introduce debug.log which gets debug.* (most of this would otherwise go
to the great bit-bucket in the sky)


# fec51ab5 03-Apr-2003 Yaroslav Tykhiy <ytykhiy@gmail.com>

Stop logging ``authpriv'' messages to the world-readable file
/var/log/messages. Such messages are for the eyes of authorized
personnel only.

PR: conf/48170
Discussed in: freebsd-security
MFC afte

Stop logging ``authpriv'' messages to the world-readable file
/var/log/messages. Such messages are for the eyes of authorized
personnel only.

PR: conf/48170
Discussed in: freebsd-security
MFC after: 2 weeks

show more ...


# a5dd613c 21-Sep-2002 Mark Murray <markm@FreeBSD.org>

Rename the ftp log filename for compatability with OpenBSD and NetBSD.

Requested by: ru


# bbd0e6a7 20-Sep-2002 Mark Murray <markm@FreeBSD.org>

Log ftpd stuff in the same way that we log lpd stuff. Too many ftpd's
are attacked for us to throw away this sort of evidence.


# 193eadc3 06-Apr-2002 Poul-Henning Kamp <phk@FreeBSD.org>

Per discussion on current: Don't spam root with syslog messages.


# 30d6457c 11-Mar-2002 Robert Watson <rwatson@FreeBSD.org>

Turns out everyone is a lot lazier than I thought. Spell
'authentication.log' as 'auth.log'.

This is also more consistent with syslog facility names.

Sigh. :-)

Submitted by: asmodai, aeonflux, gr

Turns out everyone is a lot lazier than I thought. Spell
'authentication.log' as 'auth.log'.

This is also more consistent with syslog facility names.

Sigh. :-)

Submitted by: asmodai, aeonflux, green, ....

show more ...


# 0ec9497e 11-Mar-2002 Robert Watson <rwatson@FreeBSD.org>

Clean up logging of security information a bit:

o Introduce /var/log/authentication.log, which will be the target for
auth.info and authpriv.info by default. Rotate on the same schedule
as most

Clean up logging of security information a bit:

o Introduce /var/log/authentication.log, which will be the target for
auth.info and authpriv.info by default. Rotate on the same schedule
as most other logs. Create at installation.

o Remove logging of auth.info from /var/log/security.log, which will
return to being only for security feature subsystems (such as ipfw,
and so on).

This creates a special authentication log, which can now be searched
by scripts for authentication events.

show more ...


# 179e0241 10-Mar-2002 Robert Watson <rwatson@FreeBSD.org>

/var/log/security gets almost no (if not no) activity on many FreeBSD
systems due to sshd not using the security log class. Tweak syslog.conf
so that /var/log/security also gets a useful set of
auth

/var/log/security gets almost no (if not no) activity on many FreeBSD
systems due to sshd not using the security log class. Tweak syslog.conf
so that /var/log/security also gets a useful set of
authentication-related logging.

Submitted by: aeonflux@synapse.subneural.net
MFC after: 4 weeks

show more ...


# 03b7b65a 28-Oct-2001 Jeroen Ruigrok van der Werven <asmodai@FreeBSD.org>

Explain that /var/log/all.log needs to be touched and chmod'd 'ere it
can be used.

PR: 17022
Submitted by: Niels Christian Bank-Pedersen <ncbp@bank-pedersen.dk>
MFC after: 1 week


# 1f38b566 31-Mar-2001 Murray Stokely <murray@FreeBSD.org>

Note in the comments that it is possible, but not recommended to use
spaces instead of tabs in this file. This matches the description in
the manpage.

PR: 25945
Submitted by: T. William Wells <bil

Note in the comments that it is possible, but not recommended to use
spaces instead of tabs in this file. This matches the description in
the manpage.

PR: 25945
Submitted by: T. William Wells <bill@twwells.com>

show more ...


# 960cada9 17-Feb-2001 Poul-Henning Kamp <phk@FreeBSD.org>

Log the console output to "/var/log/console.log", not "/var/log/console"
(MFC candidate)


# d9f89123 20-Dec-2000 Poul-Henning Kamp <phk@FreeBSD.org>

Add commented out entry showing use of console.info feature.


12