Feature #10865
closed
squidGuard lacks options to send traffic action logs to syslog server
Added by Kris Phillips over 3 years ago.
Updated about 1 month ago.
Description
squidGuard has options to send logs to squid's logs, but these don't seem to arrive at a syslog server and are only logged locally.
squidGuard has an option for "enable syslog" that can be added to the SquidGuard.conf file, but it's value is overwritten when any changes are made to the squidGuard config from the GUI.
It would be helpful if the logs sent to squid could be shuttled off via syslog messages or if squidGuard could send its logs directly.
- Project changed from pfSense to pfSense Packages
- Category set to squidguard
This is supported only by squidGuard-1.5-beta, see https://fossies.org/linux/www/squidGuard-1.5-beta.tar.gz/squidGuard-1.5-beta/CHANGELOG:
2009-09-15 Added a feature to send log messages to syslog based on the
patch from Jun Jiang (thank you). (bug 42) In order to use
syslog you have to run configure with the new option
"--with-syslog". In the configuration file you need to add
a line "syslog enable". If any other value but "enable" is
used syslog is disabled and logging to squidGuard.log takes
place as usual.
The following log level are used: DEBUG, NOTICE, WARN, ERROR
and EMERG. The local4 syslog facility is used by default.
If you want to change this, use the configure option
"--with-syslog-facility=<facility>".
but the current FreeBSD port version is 1.4_15: https://www.freshports.org/www/squidguard/
- Status changed from New to Rejected
With the deprecation of squid, marking this as Rejected, since this package will be removed in a future release, so it doesn't make sense to develop features like this for it.
Also available in: Atom
PDF
Updated by 
Updated by Viktor Gurov 
Updated by