You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is particularly useful when remote_syslog is run as a daemon. You could do /etc/init.d/remote_syslog start, and then immediately check for errors using something like: tail /var/log/remote_syslog.log. These errors should also be transmitted to the remote syslog server.
It wouldn't catch everything, but it's better than nothing. One particular issue is where a glob has been used, and the user that remote_syslog runs as has no access to any of the files in that directory.
The text was updated successfully, but these errors were encountered:
This is particularly useful when remote_syslog is run as a daemon. You could do
/etc/init.d/remote_syslog start
, and then immediately check for errors using something like:tail /var/log/remote_syslog.log
. These errors should also be transmitted to the remote syslog server.It wouldn't catch everything, but it's better than nothing. One particular issue is where a glob has been used, and the user that remote_syslog runs as has no access to any of the files in that directory.
The text was updated successfully, but these errors were encountered: