1*3e07920fSDavid van Moolenbroek.\" $NetBSD: syslogd.8,v 1.54 2013/01/14 03:05:41 dholland Exp $ 2*3e07920fSDavid van Moolenbroek.\" 3*3e07920fSDavid van Moolenbroek.\" Copyright (c) 1983, 1986, 1991, 1993 4*3e07920fSDavid van Moolenbroek.\" The Regents of the University of California. All rights reserved. 5*3e07920fSDavid van Moolenbroek.\" 6*3e07920fSDavid van Moolenbroek.\" Redistribution and use in source and binary forms, with or without 7*3e07920fSDavid van Moolenbroek.\" modification, are permitted provided that the following conditions 8*3e07920fSDavid van Moolenbroek.\" are met: 9*3e07920fSDavid van Moolenbroek.\" 1. Redistributions of source code must retain the above copyright 10*3e07920fSDavid van Moolenbroek.\" notice, this list of conditions and the following disclaimer. 11*3e07920fSDavid van Moolenbroek.\" 2. Redistributions in binary form must reproduce the above copyright 12*3e07920fSDavid van Moolenbroek.\" notice, this list of conditions and the following disclaimer in the 13*3e07920fSDavid van Moolenbroek.\" documentation and/or other materials provided with the distribution. 14*3e07920fSDavid van Moolenbroek.\" 3. Neither the name of the University nor the names of its contributors 15*3e07920fSDavid van Moolenbroek.\" may be used to endorse or promote products derived from this software 16*3e07920fSDavid van Moolenbroek.\" without specific prior written permission. 17*3e07920fSDavid van Moolenbroek.\" 18*3e07920fSDavid van Moolenbroek.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 19*3e07920fSDavid van Moolenbroek.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 20*3e07920fSDavid van Moolenbroek.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 21*3e07920fSDavid van Moolenbroek.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 22*3e07920fSDavid van Moolenbroek.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 23*3e07920fSDavid van Moolenbroek.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 24*3e07920fSDavid van Moolenbroek.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 25*3e07920fSDavid van Moolenbroek.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 26*3e07920fSDavid van Moolenbroek.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 27*3e07920fSDavid van Moolenbroek.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 28*3e07920fSDavid van Moolenbroek.\" SUCH DAMAGE. 29*3e07920fSDavid van Moolenbroek.\" 30*3e07920fSDavid van Moolenbroek.\" from: @(#)syslogd.8 8.1 (Berkeley) 6/6/93 31*3e07920fSDavid van Moolenbroek.\" 32*3e07920fSDavid van Moolenbroek.Dd March 28, 2012 33*3e07920fSDavid van Moolenbroek.Dt SYSLOGD 8 34*3e07920fSDavid van Moolenbroek.Os 35*3e07920fSDavid van Moolenbroek.Sh NAME 36*3e07920fSDavid van Moolenbroek.Nm syslogd 37*3e07920fSDavid van Moolenbroek.Nd log systems messages 38*3e07920fSDavid van Moolenbroek.Sh SYNOPSIS 39*3e07920fSDavid van Moolenbroek.Nm 40*3e07920fSDavid van Moolenbroek.Op Fl dnrSsTUv 41*3e07920fSDavid van Moolenbroek.Op Fl b Ar bind_address 42*3e07920fSDavid van Moolenbroek.Op Fl f Ar config_file 43*3e07920fSDavid van Moolenbroek.Op Fl g Ar group 44*3e07920fSDavid van Moolenbroek.Op Fl m Ar mark_interval 45*3e07920fSDavid van Moolenbroek.Op Fl o Ar output_format 46*3e07920fSDavid van Moolenbroek.Op Fl P Ar file_list 47*3e07920fSDavid van Moolenbroek.Oo 48*3e07920fSDavid van Moolenbroek.Fl p Ar log_socket 49*3e07920fSDavid van Moolenbroek.Op Fl p Ar log_socket2 ... 50*3e07920fSDavid van Moolenbroek.Oc 51*3e07920fSDavid van Moolenbroek.Op Fl t Ar chroot_dir 52*3e07920fSDavid van Moolenbroek.Op Fl u Ar user 53*3e07920fSDavid van Moolenbroek.Sh DESCRIPTION 54*3e07920fSDavid van Moolenbroek.Nm 55*3e07920fSDavid van Moolenbroekreads and logs messages to the system console, log files, other 56*3e07920fSDavid van Moolenbroekmachines and/or users as specified by its configuration file. 57*3e07920fSDavid van MoolenbroekThe options are as follows: 58*3e07920fSDavid van Moolenbroek.Bl -tag -width 15n 59*3e07920fSDavid van Moolenbroek.It Fl b Ar bind_address 60*3e07920fSDavid van MoolenbroekSpecify one specific IP address or hostname to bind to. 61*3e07920fSDavid van MoolenbroekIf a hostname is specified, the IPv4 or IPv6 address 62*3e07920fSDavid van Moolenbroekwhich corresponds to it is used. 63*3e07920fSDavid van Moolenbroek.It Fl d 64*3e07920fSDavid van MoolenbroekEnable debugging to the standard output, 65*3e07920fSDavid van Moolenbroekand do not disassociate from the controlling terminal. 66*3e07920fSDavid van Moolenbroek.It Fl f Ar config_file 67*3e07920fSDavid van MoolenbroekSpecify the pathname of an alternative configuration file; 68*3e07920fSDavid van Moolenbroekthe default is 69*3e07920fSDavid van Moolenbroek.Pa /etc/syslog.conf . 70*3e07920fSDavid van Moolenbroek.It Fl g Ar group 71*3e07920fSDavid van MoolenbroekSet GID to 72*3e07920fSDavid van Moolenbroek.Ar group 73*3e07920fSDavid van Moolenbroekafter the sockets and log files have been opened. 74*3e07920fSDavid van Moolenbroek.It Fl m Ar mark_interval 75*3e07920fSDavid van MoolenbroekSelect the number of minutes between ``mark'' messages; 76*3e07920fSDavid van Moolenbroekthe default is 20 minutes. 77*3e07920fSDavid van Moolenbroek.It Fl n 78*3e07920fSDavid van MoolenbroekDo not perform hostname lookups; report only numeric addresses. 79*3e07920fSDavid van Moolenbroek.It Fl o Ar output_format 80*3e07920fSDavid van MoolenbroekSelect output message format. 81*3e07920fSDavid van Moolenbroek.Bl -hang 82*3e07920fSDavid van Moolenbroek.It Em bsd , rfc3164 83*3e07920fSDavid van Moolenbroektraditional BSD Syslog format (default) 84*3e07920fSDavid van Moolenbroek.It Em syslog , rfc5424 85*3e07920fSDavid van Moolenbroeknew syslog-protocol format 86*3e07920fSDavid van Moolenbroek.El 87*3e07920fSDavid van Moolenbroek.It Fl P 88*3e07920fSDavid van MoolenbroekSpecify the pathname of a file containing a list of sockets to be 89*3e07920fSDavid van Moolenbroekcreated. 90*3e07920fSDavid van MoolenbroekThe format of the file is simply one socket per line. 91*3e07920fSDavid van Moolenbroek.It Fl p Ar log_socket 92*3e07920fSDavid van MoolenbroekSpecify the pathname of a log socket. 93*3e07920fSDavid van MoolenbroekMultiple 94*3e07920fSDavid van Moolenbroek.Fl p 95*3e07920fSDavid van Moolenbroekoptions create multiple log sockets. 96*3e07920fSDavid van MoolenbroekIf no 97*3e07920fSDavid van Moolenbroek.Fl p 98*3e07920fSDavid van Moolenbroekarguments are given, the default socket of 99*3e07920fSDavid van Moolenbroek.Pa /var/run/log 100*3e07920fSDavid van Moolenbroekis used. 101*3e07920fSDavid van Moolenbroek.It Fl r 102*3e07920fSDavid van MoolenbroekDisable the compression of repeated instances of the same line 103*3e07920fSDavid van Moolenbroekinto a single line of the form 104*3e07920fSDavid van Moolenbroek.Dq last message repeated N times . 105*3e07920fSDavid van Moolenbroek.It Fl S 106*3e07920fSDavid van MoolenbroekSync kernel messages to disk immediately. 107*3e07920fSDavid van Moolenbroek.It Fl s 108*3e07920fSDavid van MoolenbroekSelect 109*3e07920fSDavid van Moolenbroek.Dq secure 110*3e07920fSDavid van Moolenbroekmode, in which 111*3e07920fSDavid van Moolenbroek.Nm 112*3e07920fSDavid van Moolenbroekdoes not listen on a UDP socket but only communicates over a 113*3e07920fSDavid van Moolenbroek.Ux 114*3e07920fSDavid van Moolenbroekdomain socket. 115*3e07920fSDavid van MoolenbroekThis is valuable when the machine on 116*3e07920fSDavid van Moolenbroekwhich 117*3e07920fSDavid van Moolenbroek.Nm 118*3e07920fSDavid van Moolenbroekruns is subject to attack over the network and it is desired 119*3e07920fSDavid van Moolenbroekthat the machine be protected from attempts to remotely fill logs 120*3e07920fSDavid van Moolenbroekand similar attacks. 121*3e07920fSDavid van Moolenbroek.It Fl t Ar chroot_dir 122*3e07920fSDavid van Moolenbroek.Xr chroot 2 123*3e07920fSDavid van Moolenbroekto 124*3e07920fSDavid van Moolenbroek.Ar chroot_dir 125*3e07920fSDavid van Moolenbroekafter the sockets and log files have been opened. 126*3e07920fSDavid van Moolenbroek.It Fl T 127*3e07920fSDavid van MoolenbroekAlways use the local time and date for messages received from the 128*3e07920fSDavid van Moolenbroeknetwork, instead of the timestamp field supplied in the message 129*3e07920fSDavid van Moolenbroekby the remote host. 130*3e07920fSDavid van MoolenbroekThis is useful if some of the originating hosts can't keep time 131*3e07920fSDavid van Moolenbroekproperly or are unable to generate a correct timestamp. 132*3e07920fSDavid van Moolenbroek.It Fl u Ar user 133*3e07920fSDavid van MoolenbroekSet UID to 134*3e07920fSDavid van Moolenbroek.Ar user 135*3e07920fSDavid van Moolenbroekafter the sockets and log files have been opened. 136*3e07920fSDavid van Moolenbroek.It Fl U 137*3e07920fSDavid van MoolenbroekUnique priority logging. 138*3e07920fSDavid van MoolenbroekOnly log messages at the priority specified by the selector in the 139*3e07920fSDavid van Moolenbroekconfiguration file. 140*3e07920fSDavid van MoolenbroekWithout this option, messages at the specified priority or higher are 141*3e07920fSDavid van Moolenbroeklogged. 142*3e07920fSDavid van MoolenbroekThis option changes the default priority comparison from 143*3e07920fSDavid van Moolenbroek.Sq \*[Gt]= 144*3e07920fSDavid van Moolenbroekto 145*3e07920fSDavid van Moolenbroek.Sq = . 146*3e07920fSDavid van Moolenbroek.It Fl v 147*3e07920fSDavid van MoolenbroekVerbose logging. 148*3e07920fSDavid van MoolenbroekIf specified once, the numeric facility and priority are logged with 149*3e07920fSDavid van Moolenbroekeach locally-written message. 150*3e07920fSDavid van MoolenbroekIf specified more than once, the names of the facility and priority are 151*3e07920fSDavid van Moolenbroeklogged with each locally-written message. 152*3e07920fSDavid van Moolenbroek.El 153*3e07920fSDavid van Moolenbroek.Pp 154*3e07920fSDavid van Moolenbroek.Nm 155*3e07920fSDavid van Moolenbroekreads its configuration file when it starts up and whenever it 156*3e07920fSDavid van Moolenbroekreceives a hangup signal. 157*3e07920fSDavid van MoolenbroekFor information on the format of the configuration file, 158*3e07920fSDavid van Moolenbroeksee 159*3e07920fSDavid van Moolenbroek.Xr syslog.conf 5 . 160*3e07920fSDavid van Moolenbroek.Pp 161*3e07920fSDavid van Moolenbroek.Nm 162*3e07920fSDavid van Moolenbroekreads messages from the 163*3e07920fSDavid van Moolenbroek.Ux 164*3e07920fSDavid van Moolenbroekdomain socket 165*3e07920fSDavid van Moolenbroek.Pa /var/run/log , 166*3e07920fSDavid van Moolenbroekfrom an Internet domain socket specified in 167*3e07920fSDavid van Moolenbroek.Pa /etc/services , 168*3e07920fSDavid van Moolenbroekand from the special device 169*3e07920fSDavid van Moolenbroek.Pa /dev/klog 170*3e07920fSDavid van Moolenbroek(to read kernel messages). 171*3e07920fSDavid van Moolenbroek.Pp 172*3e07920fSDavid van Moolenbroek.Nm 173*3e07920fSDavid van Moolenbroekcreates the file 174*3e07920fSDavid van Moolenbroek.Pa /var/run/syslogd.pid , 175*3e07920fSDavid van Moolenbroekand stores its process 176*3e07920fSDavid van Moolenbroekid there. 177*3e07920fSDavid van MoolenbroekThis can be used to kill or reconfigure 178*3e07920fSDavid van Moolenbroek.Nm . 179*3e07920fSDavid van Moolenbroek.Pp 180*3e07920fSDavid van MoolenbroekBy using multiple 181*3e07920fSDavid van Moolenbroek.Fl p 182*3e07920fSDavid van Moolenbroekoptions, one can set up many chroot environments by passing the pathname 183*3e07920fSDavid van Moolenbroekto the log socket 184*3e07920fSDavid van Moolenbroek.Pa ( /var/run/log ) 185*3e07920fSDavid van Moolenbroekin each chroot area to 186*3e07920fSDavid van Moolenbroek.Nm . 187*3e07920fSDavid van MoolenbroekFor example: 188*3e07920fSDavid van Moolenbroek.Dl syslogd -p /var/run/log -p /web/var/run/log -p /ftp/var/run/log 189*3e07920fSDavid van Moolenbroek.Pp 190*3e07920fSDavid van MoolenbroekNote: the normal log socket must now also be passed to 191*3e07920fSDavid van Moolenbroek.Nm . 192*3e07920fSDavid van Moolenbroek.Pp 193*3e07920fSDavid van MoolenbroekThe logged message includes the date, time, and hostname (or pathname of 194*3e07920fSDavid van Moolenbroekthe log socket). 195*3e07920fSDavid van MoolenbroekCommonly, the program name and the process id is included. 196*3e07920fSDavid van Moolenbroek.Pp 197*3e07920fSDavid van MoolenbroekThe date and time are taken from the received message. 198*3e07920fSDavid van MoolenbroekIf the format of the timestamp field is incorrect, time obtained from 199*3e07920fSDavid van Moolenbroekthe local host is used instead. 200*3e07920fSDavid van MoolenbroekThis can be overridden by the 201*3e07920fSDavid van Moolenbroek.Fl T 202*3e07920fSDavid van Moolenbroekflag. 203*3e07920fSDavid van Moolenbroek.Pp 204*3e07920fSDavid van MoolenbroekAccesses from UDP socket can be filtered by libwrap configuration files, like 205*3e07920fSDavid van Moolenbroek.Pa /etc/hosts.deny . 206*3e07920fSDavid van MoolenbroekSpecify 207*3e07920fSDavid van Moolenbroek.Dq Li syslogd 208*3e07920fSDavid van Moolenbroekin 209*3e07920fSDavid van Moolenbroek.Ar daemon_list 210*3e07920fSDavid van Moolenbroekportion of the configuration files. 211*3e07920fSDavid van MoolenbroekRefer to 212*3e07920fSDavid van Moolenbroek.Xr hosts_access 5 213*3e07920fSDavid van Moolenbroekfor details. 214*3e07920fSDavid van Moolenbroek.Ss SYSLOG PROTOCOL NOTES 215*3e07920fSDavid van Moolenbroek.Nm 216*3e07920fSDavid van Moolenbroekaccepts messages in traditional BSD Syslog or in newer Syslog Protocol 217*3e07920fSDavid van Moolenbroekformat. 218*3e07920fSDavid van MoolenbroekSee RFC 3164 (BSD Syslog) and RFC 5424 (Syslog Protocol) for detailed 219*3e07920fSDavid van Moolenbroekdescription of the message format. 220*3e07920fSDavid van MoolenbroekMessages from the local kernel that are not tagged with a priority code 221*3e07920fSDavid van Moolenbroekreceive the default facility 222*3e07920fSDavid van Moolenbroek.Dv LOG_KERN 223*3e07920fSDavid van Moolenbroekand priority 224*3e07920fSDavid van Moolenbroek.Dv LOG_NOTICE . 225*3e07920fSDavid van MoolenbroekAll other untagged messages receive the default facility 226*3e07920fSDavid van Moolenbroek.Dv LOG_USER 227*3e07920fSDavid van Moolenbroekand priority 228*3e07920fSDavid van Moolenbroek.Dv LOG_NOTICE . 229*3e07920fSDavid van Moolenbroek.Sh FILES 230*3e07920fSDavid van Moolenbroek.Bl -tag -width /var/run/syslogd.pid -compact 231*3e07920fSDavid van Moolenbroek.It Pa /etc/syslog.conf 232*3e07920fSDavid van MoolenbroekThe configuration file. 233*3e07920fSDavid van Moolenbroek.It Pa /var/run/syslogd.pid 234*3e07920fSDavid van MoolenbroekThe process id of current 235*3e07920fSDavid van Moolenbroek.Nm . 236*3e07920fSDavid van Moolenbroek.It Pa /var/run/log 237*3e07920fSDavid van MoolenbroekName of the 238*3e07920fSDavid van Moolenbroek.Ux 239*3e07920fSDavid van Moolenbroekdomain datagram log socket. 240*3e07920fSDavid van Moolenbroek.It Pa /dev/klog 241*3e07920fSDavid van MoolenbroekThe kernel log device. 242*3e07920fSDavid van Moolenbroek.El 243*3e07920fSDavid van Moolenbroek.Sh SEE ALSO 244*3e07920fSDavid van Moolenbroek.Xr logger 1 , 245*3e07920fSDavid van Moolenbroek.Xr syslog 3 , 246*3e07920fSDavid van Moolenbroek.Xr services 5 , 247*3e07920fSDavid van Moolenbroek.Xr syslog.conf 5 , 248*3e07920fSDavid van Moolenbroek.Xr newsyslog 8 249*3e07920fSDavid van Moolenbroek.Rs 250*3e07920fSDavid van Moolenbroek.%R RFC 251*3e07920fSDavid van Moolenbroek.%N 3164 252*3e07920fSDavid van Moolenbroek.%D August 2001 253*3e07920fSDavid van Moolenbroek.%T The BSD syslog Protocol 254*3e07920fSDavid van Moolenbroek.Re 255*3e07920fSDavid van Moolenbroek.Rs 256*3e07920fSDavid van Moolenbroek.%R RFC 257*3e07920fSDavid van Moolenbroek.%N 5424 258*3e07920fSDavid van Moolenbroek.%D March 2009 259*3e07920fSDavid van Moolenbroek.%T The Syslog Protocol 260*3e07920fSDavid van Moolenbroek.Re 261*3e07920fSDavid van Moolenbroek.Sh HISTORY 262*3e07920fSDavid van MoolenbroekThe 263*3e07920fSDavid van Moolenbroek.Nm 264*3e07920fSDavid van Moolenbroekcommand appeared in 265*3e07920fSDavid van Moolenbroek.Bx 4.3 . 266*3e07920fSDavid van MoolenbroekSupport for multiple log sockets appeared in 267*3e07920fSDavid van Moolenbroek.Nx 1.4 . 268*3e07920fSDavid van Moolenbroeklibwrap support appeared in 269*3e07920fSDavid van Moolenbroek.Nx 1.6 . 270*3e07920fSDavid van MoolenbroekSupport for RFC 5424, TLS encryption and authentication, signed messages 271*3e07920fSDavid van Moolenbroekappeared in 272*3e07920fSDavid van Moolenbroek.Nx 6.0 . 273