########
# rsyslog.conf configuration created by What::Node::Rsyslog
# Do not edit!  Hand-made changes will be lost!
########
#rsyslog v3 config file

# if you experience problems, check
# http://www.rsyslog.com/troubleshoot for assistance

#### MODULES ####

$ModLoad imuxsock.so    # provides support for local system logging (e.g. via logger command)
$ModLoad imklog.so      # provides kernel logging support (previously done by rklogd)

# Use default timestamp format
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat

########
# what-generated entries follow
########
authpriv.*                               /var/log/secure
local7.*                                 /var/log/boot.log
cron.*                                   /var/log/cron
*.info;mail.none;authpriv.none;cron.none /var/log/messages
mail.*                                   /var/log/maillog
########
# end of what-generated entries
########

# ### begin forwarding rule ###
# The statement between the begin ... end define a SINGLE forwarding
# rule. They belong together, do NOT split them. If you create multiple
# forwarding rules, duplicate the whole block!
# Remote Logging (we use TCP for reliable delivery)
#
# An on-disk queue is created for this action. If the remote host is
# down, messages are spooled to disk and sent when it is up again.
$WorkDirectory /var/spool/rsyslog # where to place spool files
$ActionQueueFileName fwdRule1 # unique name prefix for spool files
$ActionQueueMaxDiskSpace 1g   # 1gb space limit (use as much as possible)
$ActionQueueSaveOnShutdown on # save messages to disk on shutdown
$ActionQueueType LinkedList   # run asynchronously
$ActionResumeRetryCount -1    # infinite retries if host is down
# remote host is: name/ip:port, e.g. 192.168.0.1:514, port optional
*.* @loghost:514
*.* @@larch:514
#above changed to single at for UDP which appears to work
### end of the forwarding rule ###


