summaryrefslogtreecommitdiffstats
path: root/usr.sbin/syslogd
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix all the spelling mistakes I could find in the man pages for wordskeramida2005-07-311-1/+1
| | | | | | | | that have at least 3 characters. MFC after: 1 week Thanks to: Music band ``Chingon'' for keeping me company while searching for these.
* Add cases for ENOBUFS and ENETDOWN. We need to make sure that wecsjp2005-05-191-0/+2
| | | | | | | | | catch all transient errors. This fixes situations where transient error conditions such as network interfaces losing carrier signals or the system running out of mbufs would result in the permanent removal of forwarding syslog messages. MFC after: 1 week
* NI_WITHSCOPEID cleanup. Neither RFC 2553 nor RFC 3493 definesume2005-05-131-17/+5
| | | | | NI_WITHSCOPEID, and our getaddrinfo(3) does nothing special for it, now.
* Add -S option which allows to change the pathname of the privilegedhrs2005-04-132-2/+11
| | | | | | | socket /var/run/logpriv. Reviewed by: glebius and kensmith MFC after: 2 days
* Check that supplied facility is not bigger than LOG_NFACILITIES.glebius2005-03-281-0/+7
| | | | | PR: bin/79260 Submitted by: Shuichi KITAGUCHI
* Expand contractions.ru2005-02-131-2/+2
|
* Expand *n't contractions.ru2005-02-132-3/+3
|
* Sort sections.ru2005-01-181-21/+21
|
* Scheduled mdoc(7) sweep.ru2005-01-111-4/+1
|
* Allow ':' and '%' in hostname specifications so that we can specify IPv6dwmalone2004-12-281-1/+1
| | | | | | addresses and scope IDs. MFC after: 3 weeks
* Some syslog messages delimit the program tag with whitespace ratherdwmalone2004-12-281-2/+2
| | | | | | | | | | | | than a colon, so don't allow whitespace in program names. To be consistent with hostnames, don't allow whitespace in the program name specifiers in syslog.conf either. (The first change is by Markus from the PR, the second is mine.) PR: 68691 Submitted by: Markus Oestreicher <m.oe@x-trader.de> MFC after: 3 weeks
* s/priveleged/privileged/glebius2004-11-181-1/+1
|
* Fix a minor comment typo: priveleged = privileged.keramida2004-11-181-1/+1
|
* Really revert the whitespace change to usage().ru2004-11-111-3/+3
|
* Change TABs back to spaces in usage string constants.glebius2004-11-111-3/+3
| | | | Requested by: ru
* Whitespace.glebius2004-11-111-11/+11
| | | | Approved by: cvs diff -b
* Double receive buffer size on sockets.glebius2004-11-111-1/+18
| | | | | | | | PR: bin/72366 Ok'd by: dwmalone Approved by: julian (mentor) Obtained from: OpenBSD MFC after: 1 month
* Bump document date.kensmith2004-11-091-1/+1
| | | | | | Noticed by: trhodes Pointy hat: kensmith MFC after: 1 week
* Add newsyslog(8) to the "See Also" section.kensmith2004-11-091-1/+2
| | | | MFC after: 1 week
* Protect against local flooder of /var/run/log. Do not loop forever inglebius2004-11-042-5/+14
| | | | | | | | | | | | | syslog(3) if we are a priveleged program (sshd, su, etc.). - Make syslogd open an additional socket /var/run/logpriv, with 0600 permissions. - In libc, try to use this socket. - Do not loop forever if we are using this socket (partial backout of 1.31) Reviewed by: dwmalone, Andrea Campi <andrea webcom it> Approved by: julian (mentor) MFC after: 1 month
* - Use stailqueue for sockets instead of socket buffer. Thusglebius2004-11-042-41/+82
| | | | | | | | | remove limit for 20 sockets. - Add possibility to specify file mode for sockets created with '-l'. - Check that socket name in '-l' is absolute. Reviewed by: dwmalone, Andrea Campi <andrea webcom it> Approved by: julian (mentor)
* Per letter dated July 22, 1999 remove 3rd clause of Berkeley derived softwareimp2004-08-074-16/+1
| | | | (with permission of addtional copyright holders where appropriate)
* Fix dofsync() declaration.cperciva2004-07-041-1/+1
| | | | Pointed out by: dwmalone
* Where syslogd would have fsync()ed a file in the past, instead set a flagcperciva2004-07-041-3/+25
| | | | | | | | | | | FFLAG_NEEDSYNC and fsync the file when select() next returns zero. This dramatically speeds up the process of logging large amounts of data, while leaving the essential semantics (that data can be expected to be on disk if we crash) unchanged. In my tests, this speeds up the rc phase of booting by 18-20%. [1] YES PLEASE! by: phk [1]
* Eliminated double whitespace.ru2004-07-031-1/+2
|
* Mechanically kill hard sentence breaks.ru2004-07-022-23/+46
|
* Also terminate program names if we hit a '/' - this is to be slightlydwmalone2004-05-301-1/+2
| | | | | | | more friendly to postfix log messages. PR: 50912 Submitted by: Stanislav Lapshansky <slapsh@slapsh.pp.ru>
* A log file name may now be prefixed by a '-' if it should not bedwmalone2004-05-302-2/+32
| | | | | | | | | | | | | explicitly fsynced after kernel messages are logged. This option should be syntax compatible with a similar option in Linux syslogd. I've made some small changes to Pekka's patch, hoepfully I haven't goofed anything. PR: 66790 Submitted by: Pekka Savola <pekkas@netcore.fi> Obtained from: Martin Schulze's syslogd MFC after: 1 month
* Try to be more careful about using using the file descriptor f_file.dwmalone2004-05-301-7/+13
| | | | | | | | | | | | | | | | | | | | | Syslogd should ensure that f_file is a valid file descriptor when f_type is FILE, CONSOLE, TTY and for a PIPE where f_pid > 0. If the descriptor is closed/invalid then the type should be set to UNUSED or the pid should be set to 0. To this end: 1) Don't close(f->f_file) if we can't send a message to a remote host because the file descriptor used for remote logging is stored in finet, not in f->f_file. f->f_file is probably uninitialised, so I guess we usually end up closing fd 0. 2) Don't close PIPE file descriptors if they are invalid. 3) If the call to p_open fails, don't set the pid. The OpenBSD patches in this area set f_file to -1 after the fd is closed and then avoids calling close if f_file < 0. I haven't done this, but it might be a good idea too. Inspired by: PR 67139/OpenBSD
* Some string fixes.dwmalone2004-05-291-4/+9
| | | | | | | | | | | 1) Use strncpy on strings out of utmp. 2) Avoid running off the start of one string while removing white space. (I've used slightly different code to OpenBSD here.) 3) Ignore trailing spaces in the priority. PR: 67139 Submitted by: Xin LI <delphij@FreeBSD.org.cn> Obtained from: OpenBSD
* Exit with a warning if the path to one of the logging sockets isdwmalone2004-05-291-0/+4
| | | | | | | too long, rather than silently truncating them. PR: 67139 Inspired by: OpenBSD
* Fix some bugs that don't manifest themselves in practice.dwmalone2004-05-291-3/+6
| | | | | | | | | | | | 1) Don't check for getopt returning '?', we have a default case. 2) Check if the priority is LOG_KERN correctly - in practice LOG_KERN is 0, so it makes no difference. OpenBSD fixed a different nearby bug that we don't have 'cos our definition of LOG_MAKEPRI is different to OpenBSD's. Copy a comment from OpenBSD, observing that LOG_KERN is 0. Inspired by PR: 67139
* Update a couple of comments.dwmalone2004-05-291-2/+2
| | | | | | PR: 67139 Submitted by: Xin LI <[3]delphij@FreeBSD.org.cn> Obtained from: OpenBSD
* Silence some constness and printf type warnings. Most of thedwmalone2004-05-261-12/+14
| | | | | const fixes are ugly 'cos the types in an iovec aren't quite right for a writev.
* Fixed style of DPADD and LDADD assignments as per style.Makefile(5).ru2004-02-051-2/+2
|
* Use strtol to parse the <%d> tags in printline() and printsys().iedowse2004-01-311-18/+18
| | | | | | Sort local variables declarations in these functions. Submitted by: bde
* Be much more strict about parsing tagged log messages from /dev/klog;iedowse2004-01-261-10/+20
| | | | | | | | | | | | if the line doesn't match ^<%d>, then treat it as a regular kernel printf line. Previously if a kernel printf message started with "<" it would be interpreted as a log message, often with LOG_EMERG level. This was triggered by some printfs in sys/dev/aic7xxx/, and can also happen with the partial lines that result if syslogd cannot keep up with the rate of arrival of kernel messages. Reviewed by: dwmalone MFC after: 1 week
* logerror is used in syslogd to log errors from syslogd itself. Itdwmalone2003-11-161-0/+6
| | | | | | | | | | | | is possible for an error to occur while trying to log an error, and this can result in infinite recursion (or at least until we run out of stack). Rather than this, we ignore requests to log an error while logging an error. PR: 51253 MFC after: 2 weeks
* Remove an argument to printf that is unused.dwmalone2003-11-161-1/+1
|
* mdoc(7): Use the new feature of the .In macro.ru2003-09-081-1/+1
|
* Avoid a corrupt timestamp on the consolegshapiro2003-05-171-2/+6
| | | | | | | PR: 51587 Submitted by: Dmitry Sivachenko <mitya@cavia.pp.ru> Approved by: re (rwatson) MFC after: 3 days
* Avoid code duplication by using libutil's trimdomain() instead ofgshapiro2003-05-172-10/+7
| | | | | | | | | an incorrect re-implementation. PR: 52223, 52342 Submitted by: Dan Nelson <dnelson@allantgroup.com> Approved by: re (bmah/rwatson) MFC after: 2 days
* Cleanup hostname matching in syslogd:gshapiro2003-05-041-17/+24
| | | | | | | | | | | | | | | | | | | 1. Hostnames were not treated case insensitively in all cases. 2. The method for stripping hostnames when reading the syslog.conf differed from that when finding the hostname of an incoming request. This lead to a broken match check. In my case, it meant I had to have '@scooter.smi.example.com.example.com' to have 'logger.example.com' properly save messages from 'scooter.smi.sendmail.com'. 3. Add paranoia to cfline() such that it doesn't try to access memory outside of the bounds of the f_host string. 4. While I am here, get rid of an outdated comment, argv[{0,1,2}] are now checked for NULL after the strdup() calls. Reviewed by: dwmalone MFC after: 1 week
* style.Makefile(5)obrien2003-04-041-1/+1
|
* Hostname specifications must allow commas in the value. They arethomas2003-02-211-1/+2
| | | | | | | used to separate multiple host names. Noted by: Dan Nelson <dnelson@allantgroup.com> Reviewed by: roberto
* Allow multiple hosts or programs to be named in programthomas2003-02-132-6/+39
| | | | | | | | | | | | | or host specifications, eg: !foo,bar *.* /var/log/only_foo_or_bar.log !-foo,bar *.* /var/log/all_except_foo_or_bar.log Reviewed by: roberto Not objected to by: arch@
* Various language tweaks.trhodes2002-12-241-17/+17
| | | | | PR: 45604 Submitted by: Chris Pepper <pepper@rockefeller.edu>
* Uniformly refer to a file system as "file system".ru2002-12-122-2/+2
| | | | Approved by: re
* mdoc(7) police: markup fixes.ru2002-11-272-4/+4
| | | | Approved by: re
* Factor out the code that determines whether a message must be skippedthomas2002-11-071-26/+27
| | | | | | | as a consequence of a host or program name specification into a common function, skip_pmessage. Reviewed by: roberto
OpenPOWER on IntegriCloud