Dansguardian and clamav

rjcrowder

Just a little more info on this… it appears that the install is not creating the clamav-freshclam and clamav-clamd scripts in /usr/local/etc/rc.d. I verified they were not created on a fresh install. Because clamav-clamd is not created, the proper clam directories are not created by the dansguardian.inc code (in /usr/local/pkg).

In order to fix it, I copied clamav-freshclam and clamav-clamd from an old 2.0.3 install...

asterix

I have been requesting a fix for this since a while now.

http://forum.pfsense.org/index.php/topic,63485.0.html

rjcrowder

@asterix:

I have been requesting a fix for this since a while now.

http://forum.pfsense.org/index.php/topic,63485.0.html

Yea… it seems to be a problem with the install. Trying to remember for sure, but I believe the things that I did to get it working were the following...

1. Create the directories necessary for freshclam to run. I believe that was /var/log/clamav and /var/db/clamav. Made the owner:group "clamav:nobody" for both.
2. Copy the freshclam and clamav-clamd scripts from an old install of 2.0.3 into /usr/local/etc/rc.d

asterix

yeah but for normal users we need a fix :)

kejianshi

Yeah - Generally speaking, if you have to dig through config files and get all command-line to make something go, its not a solution for the masses.

rjcrowder

@asterix:

yeah but for normal users we need a fix :)

OK… I understand the need for a fix. I also acknowledge that not everyone has the background to debug these types of issues and make manual changes to resolve the problem. However (at the risk of sounding defensive of Marcello), I believe that all of the pfSense packages are freely developed and freely provided. I doubt he is guaranteed any compensation for his work and probably receives a pittance in donations.

With that in mind, I think we all have an obligation to do the following:
1.) Be patient, I'm sure debugging the install of DG on pfSense (especially on an RC) isn't Marcello's full-time job.
2.) Help with the testing, debugging and/or coding process if we have that capability.
3.) Contribute monetarily if we use the package and have the means

In addition, I'd point out that 2.1 is still a release candidate. It is not reasonable to expect that all packages are going to install and work fine on it. Likewise, since it is not "production" code, it isn't reasonable to expect fixes in a timely manner.

Just my two cents.

asterix

Hey.. no one is saying Marcello is the only one who needs to fix this. ;) We can all work up something and come up with a working fix which he can then incorporate to the package and update it for everyone :)

rjcrowder

@asterix:

Hey.. no one is saying Marcello is the only one who needs to fix this. ;) We can all work up something and come up with a working fix which he can then incorporate to the package and update it for everyone :)

Good point… I've made (and submitted to GIT) a few changes. I'm not familiar with how the install stuff works though. Would you (or anyone for that matter) be able to give me a quick overview? Or point me in the best place to look to get started?

marcelloc

Thanks rjcrowder for your words, I really appreciate it. :)

I'm currently really busy at work and having no free time to check what is going wrong but I have a working 2.1 beta with dansguardian. As soon as I have time I'll check it.

For those who wants to make a donation, ask for my PayPal account in private.

rjcrowder

@rjcrowder:

Would you (or anyone for that matter) be able to give me a quick overview? Or point me in the best place to look to get started?

so… it looks to me like the problem must be in the install of the clamav package (see /var/db/pkg/clamav-0.97.6). Likewise, I'd conjecture that the problem is based on something that is done via the "+CONTENTS" file... Can anyone give me a clue how this is used / interpreted during the install process?