On Wed, Dec 21, 2011 at 11:58 AM, greg whynott <[email protected]>wrote:
> after re-installing squid3 twice, we still see this in the logs: > > Dec 21 11:34:28 pfw01 php: /pkg_mgr_install.php: Starting Squid > Dec 21 11:34:28 pfw01 php: /pkg_mgr_install.php: The command > '/usr/local/sbin/squid' returned exit code '127', the output was > '/usr/local/sbin/squid: not found' > > and sure enough the squid binary is not there.. > > removing squid3 and reinstalling it fixed things. It retained the > previous config too, which was nice. > > now to research how to use both features at once. shouldn't be an > issue even if they are different versions, one is binding to the > external interface whereas the other is not.. > > -g > > > > > > On Wed, Dec 21, 2011 at 11:45 AM, greg whynott <[email protected]> > wrote: > > I just got burnt installing a package, which made alot of people sad > > for a little while. thought i'd share, perhaps it'll save someone > > from doing the same. > > > > Been using the squid3 package for some time, recently we decided to > > allow external access into our Exchange web mail interface. I > > installed the 'squid-reverse' package, the description claims was > > designed for this exact requirement. Doing so caused it to break > > the already installed squid3 which the business is using. removing > > the squid-reverse package didn't correct anything, squid wouldn't > > restart. After re-installing squid3 package we still don't have > > proxy services. > > > > I am now in the process of sorting it out, still. Thankfully we > > are using transparent with redirect, which i turned off till this > > gets resolved. > That's probably not going to work - I don't think anyone ever intended for two version of squid to be on one system. Besides, why not just port forward exchange through the firewall - there is no need for squid to do this. Scott
_______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
