Your hardware will easily run ClearOS. I've been running similar config for several years.
Content filtering for https traffic is not easy because it is encrypted by design. Having said that you can blacklist categories and so on.
My suggestion is that you set up a system and have a play and see if you can make it do what you seek to achieve.
Fantastic - thanks for the feedback... There are quite of number of changes and bug fixes from 2.3.1 -> 2.3.10, especially two removing a 2G size limitation.
I have updated the instructions on my site to reflect the newer rpm...
The source files, for anybody interested, is available at :-
Have made a newer version than that available on rpmforge :-
OK - new rpm created and the instructions at the beginning of this append updated (as well as the subject) for both Versions 6 and 7 of ClearOS.
Duncan - in your case as you already has sarg installed it should do an upgrade... However, there were some new options added to the config file /etc/sarg/sarg.conf, so I recommend you (and any body-else with a prope version) rename yours and edit the new one with any changes you want to make. Let me know how you go. I followed the instructions and it worked for me - so hopefully you meet with the same success. As to the buffer overflow - we will see...
OK - the rpm for Version 7 was built using sarg-2.3.10 source.
That includes some fixes that might or might not solve you problem...
It would take a few minutes to make an rpm based on sarg-2.3.10 for ClearOS 6.7 x86_64
Do you want it?
For anyone coming across this thread, before repairing the proc table as one of the post in here advises, can you try:
And upgrade to 2.1.7-1.
Then, try restarting Zarafa server:
And report back here and let me know if that too, resolves the proc issue.
Also, if anyone who had the 'proc' corruption in the past, upgrading may prevent the issue from occurring in the future.
According to this thread on the Zarafa forums, we should have this issue with the version of MariaDB we're running...however, we should have been running the mysql_upgrade script when upgrading the internal database.
All this update does it provide an automated script that will run the mysql_upgrade command.
That you can also run with the --force flag, if desired.
It does nothing if nothing is required, so a fairly innocuous script.
I'd like to know two things:
1. Confirm that running this script fixes the proc table corruption
2. Longer term, I'd like to hear back on users who have upgraded, whether they ever see the proc corruption again or not...ideally, this issue 'goes away'. If it occurs to users who have upgraded, but #1 confirms it repairs the proc table, my next step is to add the calling of this script to the Zarafa server stop/start, that will fix the situation when the user tries starting Zarafa server.