summaryrefslogtreecommitdiffstats
path: root/etc/syslog.conf
Commit message (Collapse)AuthorAgeFilesLines
* Make sure debug.log only gets debugging messages.des2003-04-231-1/+1
|
* Introduce debug.log which gets debug.* (most of this would otherwise godes2003-04-081-0/+1
| | | | to the great bit-bucket in the sky)
* Stop logging ``authpriv'' messages to the world-readable fileyar2003-04-031-1/+1
| | | | | | | | | /var/log/messages. Such messages are for the eyes of authorized personnel only. PR: conf/48170 Discussed in: freebsd-security MFC after: 2 weeks
* Rename the ftp log filename for compatability with OpenBSD and NetBSD.markm2002-09-211-1/+1
| | | | Requested by: ru
* Log ftpd stuff in the same way that we log lpd stuff. Too many ftpd'smarkm2002-09-201-0/+1
| | | | are attacked for us to throw away this sort of evidence.
* Per discussion on current: Don't spam root with syslog messages.phk2002-04-061-3/+0
|
* Turns out everyone is a lot lazier than I thought. Spellrwatson2002-03-111-1/+1
| | | | | | | | | | 'authentication.log' as 'auth.log'. This is also more consistent with syslog facility names. Sigh. :-) Submitted by: asmodai, aeonflux, green, ....
* Clean up logging of security information a bit:rwatson2002-03-111-1/+2
| | | | | | | | | | | | | 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.
* /var/log/security gets almost no (if not no) activity on many FreeBSDrwatson2002-03-101-1/+1
| | | | | | | | | 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
* Explain that /var/log/all.log needs to be touched and chmod'd 'ere itasmodai2001-10-281-0/+1
| | | | | | | | can be used. PR: 17022 Submitted by: Niels Christian Bank-Pedersen <ncbp@bank-pedersen.dk> MFC after: 1 week
* Note in the comments that it is possible, but not recommended to usemurray2001-03-311-1/+4
| | | | | | | | spaces instead of tabs in this file. This matches the description in the manpage. PR: 25945 Submitted by: T. William Wells <bill@twwells.com>
* Log the console output to "/var/log/console.log", not "/var/log/console"phk2001-02-171-2/+2
| | | | (MFC candidate)
* Add commented out entry showing use of console.info feature.phk2000-12-201-0/+2
|
* Add two commented out syslog.conf entries, one to demonstrate the use ofrwatson2000-02-081-0/+4
| | | | | | | | | | | | | | an all.log for logging all messages, and one to demonstrate use of loghosts. Also, a matching entry in newsyslog.conf for all.log. Per request of Garrett Wollman, also modified the maillog entry to use the @T newsyslog time specification mechanism. Because newsyslog doesn't support the mod date specification machanism, couldn't change other entries that required more than one execution a month, but less than once a day. Approved by: jkh Reviewed by: freebsd-security
* Move /var/cron/log to /var/log/cronn_hibma1999-09-061-1/+1
|
* $Id$ -> $FreeBSD$peter1999-08-271-1/+1
|
* This is the addition of a syslog(3) security.* top-level category. Thisgreen1999-08-211-1/+2
| | | | | | | | | should be used from now on for anything security but not auth-related. Included are updates for all relevant manpages and also to /etc files, creating a new /var/log/security. Nothing in the system logs to /var/log/security yet as of the time of this commit. Reviewed by: rgrimes, imp, chris
* - Add a couple comment lines to note that spaces are not allowed asnate1998-10-141-1/+3
| | | | | | | field separators. PR: conf/8162 Submitted by: Sheldon Hearn <sheldonh@axl.training.iafrica.com>
* Add Id keywordsbrian1998-09-021-0/+2
|
* Add ppp.logache1997-06-101-0/+2
|
* auth.debug should not be sent to root realtimepst1996-11-061-2/+6
| | | | | | | news.notice info should not be sent to /var/log/messages, as news has its own set of logs and notice is overused by inn added entries for newsservers (but they're commented out)
* Back out daemon.* addition, ssh port should be fixed insteadache1996-11-021-1/+1
|
* Log daemon.* to /var/log/messages or very valuable daemons messagesache1996-10-311-1/+1
| | | | lost forever
* Put startslip syslog messages into separate fileache1996-01-071-0/+2
| | | | | Increase rotating log sizes in newsyslog.conf to reflect more common case
* This is Vixie cron 3.0. This version fixes all known security bugs.guido1994-01-221-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | Further it implements crontab -e. I moved cron from /usr/libexec to /usr/sbin where most daemons are that are run from rc. That also gets rid of the ugly path crond used to have in ps(1) outputs. Further I renamed it to cron, as Paul Vixie likes it and is done by NetBSD. NOTE VERY WELL THE FOLLOWING: 1) Systems crontab changed. Every users crontab resides in /var/cron *EXCEPT* root's. This is a special crontab as it resides in /etc. Further it is the *ONLY* crontab file in which you specify usernames. See /usr/src/etc/crontab. This is also done by BSDI's BSD/386 as far as I know (they provided the patches for it anyway) 2) So you *must* delete root's crontab and reinstall the copy in /etc from /usr/src/etc. 'Must' is to much: the old installed crontab will work but cron will also try to 'run' /etc/crontab. 3) Last but not least: cron's logging is now done via syslog. Note that logging by cron is done lowercase when it logs about itsself and uppercase when it logs user events, like installing a new crontab. The default logfile file is the same as before: syslog.conf:cron.* /var/cron/log -Guido
* Initial import of 386BSD 0.1 othersrc/etcrgrimes1993-06-201-0/+8
OpenPOWER on IntegriCloud