Squidguard on 2.1
-
squid3 and squidguard are marked as "working".
They are working - or service is starting (did no further tests) - but they are using the worng folder paths.
For squid3 this was fixed here by marcelloc:
https://github.com/bsdperimeter/pfsense-packages/commit/9e75101f03fee241a3163473c7f427d28d0539bdFor SqudGuard it needs the same folder check fixes.
Service is starting but it does not find squid.conf in the correct folder. -
Try this file for squidguard_configurator.inc
http://files.chi.pfsense.org/jimp/squidguard_configurator.inc.txt
I don't have time to test it myself this morning, and I didn't want to blindly commit that to such a popular package.
-
Both services are running, no error output on syslog for a missing file.
Restarted the services, made changes on both und saved and applied them.
So what I can see from GUI it is running but didn't do any further tests.But I get this on syslog (pfsense 2.1 amd64) - not sure how important this output really is:
Oct 11 17:29:17 squid[43820]: Squid Parent: child process 44118 started Oct 11 17:29:15 php: /status_services.php: The command '/usr/local/etc/rc.d/squid.sh stop' returned exit code '1', the output was 'squid: No running copy' Oct 11 17:29:10 php: /status_services.php: The command '/usr/local/etc/rc.d/squid.sh stop' returned exit code '1', the output was '' Oct 11 17:29:10 squid[5272]: Squid Parent: child process 17570 exited with status 0 Oct 11 17:29:00 syslogd: kernel boot file is /boot/kernel/kernel
On pfsense 2.0.1 I do not get such an error on system log. Services are running, too.
-
OK. but you did see errors before? Without the file I posted?
That service error probably isn't anything to worry about.
-
OK. but you did see errors before? Without the file I posted?
That service error probably isn't anything to worry about.
Yes, before there was an error complaining about a .conf file I do not remember anymore which was missing. This error does not appear anymore.
-
OK I went ahead and committed that file. If you (or anyone else) gets a chance to test it more extensively, post here if there are more errors/problems.