| Appendix |
350
To redirect Aspera logging, modify
/etc/syslog.conf
(
/etc/rsyslog.conf
in the case of Red Hat or
CentOS 6.XA) and add
local2.none
to the
/var/log/messages
line. For example, if you have the following
line:
*.info;mail.none;authpriv.none;cron.none /var/log/messages
Change it to:
*.info;mail.none;authpriv.none;cron.none;local2.none /var/log/messages
Next, forward
local2.info
log messages to your new file. For example, to write to
/var/log/aspera.log
,
add the following line just below the line you modified above:
local2.info -/var/log/aspera.log
The log file name should be separated from the log facility (
local2.info
) by tab characters, not spaces and be
preceded by a hyphen. The hyphen before the log file name allows for asynchronous logging.
Next, restart the syslog daemon to have it load the new configuration:
# service syslog restart
In the case of Red Hat or CentOS 6.X:
# service rsyslog restart
Your Aspera log messages now appear in
/var/log/aspera.log
instead of
/var/log/messages
.
SLES (Suse) systems
On SLES (Suse) systems, the transfer logs are recorded in the following system log file:
/var/log/
localmessages
To redirect Aspera logging, locate the following section in
/etc/syslog-ng/syslog-ng.conf
:
filter f_local { facility(local0, local1, local2, local3, local4, local5,
local6, local7); };
destination localmessages { file("/var/log/localmessages"); };
log { source(src); filter(f_local); destination(localmessages); };
Modify the section as follows:
filter f_local { facility(local0, local1, local3, local4, local5, local6,
local7); };
filter f_aspera { facility(local2); };
destination localmessages { file("/var/log/localmessages"); };
log { source(src); filter(f_local); destination(localmessages); };
destination asperalog { file("/var/log/aspera.log"); };
log { source(src); filter(f_aspera); destination(asperalog); };
Then run the following command:
# rcsyslog restart
Your Aspera log messages now appear in
/var/log/aspera.log
instead of
/var/log/localmessages
.
