Enable/Run Squid3 after installation
-
Dear all,
Or I'm missing it, but where -after installation of Squid3- can I enable this service? Formerly it was just a checkbox for toggling between enable/disable. If that gone?
Than another thing. When I try to restart services from 'Status->Services' like Squid3 and others, restart is not functioning. It disables that specific service but do not get it online again. What's happening?
I get a message that's indicating the service is started, but no 'green icon' after refreshing the page. Are these buttons working?Thanks a lot,
Canefield -
This package does not has an enable/disable button yet. I think it will stop daemon if you do not select any interface, but I didn`t tested.
I'm not sure what is happening with service tab but if you need to restart/reload the daemon, just save config on gui to force it.
att,
Marcello Coutinho -
Dear all,
Or I'm missing it, but where -after installation of Squid3- can I enable this service? Formerly it was just a checkbox for toggling between enable/disable. If that gone?
Than another thing. When I try to restart services from 'Status->Services' like Squid3 and others, restart is not functioning. It disables that specific service but do not get it online again. What's happening?
I get a message that's indicating the service is started, but no 'green icon' after refreshing the page. Are these buttons working?Thanks a lot,
CanefieldSquid3 does report proper status on the services screen. I'd recommend that you ssh into the box and check the running status of squid (ps -ax | grep squid). If it is not running, then try to start it manually and see what happens. Prob start with "squid -k parse" to make sure it parses the config file correctly. You may need to go into the service and make some setting changes in order to get it to start.
As far as other services, the only one I've had issue with it showing proper status is "vhosts". You can search the forums to find a workaround that forces it to show the correct status.
-
Squid3 does report proper status on the services screen.
The status is showing up ok, the problem I see is when you try to start or restart the daemon.
I'll take a look if I did some mistake on squid service info.EDIT:
I found a way to fix it. The pfsense function that stops daemon is running on backgroud when it should wait process to killed before trying to start/restart.
I did pull request to try to fix this. On my tests, it worked.
att,
Marcello Coutinho