[quote=“G0dzilla, post: 35883, member: 1692”]After the resolv.conf file is added to the init.xz it still needs entries in it for DNS to work.
This can be done manually or with a program like udhcpc.
This can all be done in a debug task - followed by the command “freshclam” to see if clamav can update. This may not work still, but should get the DNS working at least.
I believe the database files are left out to save space in the init.xz .
The init.xz file is currently limited to 57MB I think.
Here is info on increasing it - [url]http://fogproject.org/forum/threads/change-initrd-size.3920/[/url]
I think a more ideal solution for Clam with FOG would be for the clients to download the database files from the local fog server instead of going out on the internet for them. It would involve a bit more manual customizing for each server tho. I think virus scanning with FOG is just a cool feature - but isn’t really important.
You can always try Trinity Rescue Kit for scanning, that has 4-5 scanners built in and can be PXE booted.
There is also a script available to run all the scanners.
remy_virusscan - Offers the ability to update all scanners at once and then scan all attached drives with the updated scanners in a silent mode. Scanners include Avast!, BDE, CHKRootkit, ClamAV, F-Prot, RKHunter and Vexira.[/quote]
I know a little bit about servers. I set the nameserver entry to 22.214.171.124 (Google name server). I also tried my two internal DNS servers. Neither Google nor my internal servers worked. I didn’t though add search or domain directives to resolv.conf, are they necessary for this implementation?
It’s possible to PXE boot from two different systems? i.e. Fog and AV Offline Scan.