https://bugzilla.novell.com/show_bug.cgi?id=223772 ------- Comment #1 from max@novell.com 2006-11-28 06:12 MST ------- (In reply to comment #0)

Manual execution of feshclam requires access to TCP Port 3310.

That's port 3310 on localhost (127.0.0.1) and the maintainer of SuSEfirewall2 just confirmed that it doesn't block anything on localhost by default. There is an error message about port 3310 when freshclam is started while clamd is not running, but that can be safely ignored, as it only means that freshclam wasn't able to notify clamd of the database change.

Unless this port is opened manually in SUSE firewall Advanced enabling it as a daemon in system services will result in an incomplete new database being auto downloaded.

As the access to localhost:3310 happens *after* the download of the virus database files, I don't see why failing to connect should cause the download to be incomplete.

Some mechanism for Opening Port 3310 and/or including it as a firewall 'service' to be opened rather than use advanced needs to be made for those who activate the daemon.

Not needed, see above.

There is also the perception in email conversations that clamAV is only required to protect MS-Windows hosts connected to a SUSE Server - Documentation suggests otherwise.

I don't know what email conversations you are referring to, but filtering away viruses is always a good idea. Up to this point, I'd close this bug as INVALID, but for the KlamAV part, I'll pass it on to our KDE maintainers. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=223772 ------- Comment #5 from alpha096@tpg.com.au 2006-11-28 10:54 MST ------- With respect to

Are you really sure that it is permitting this access that makes the difference? Notice that the connection to 127.0.0.1 is only tried if the database files did actually get an update in the current run. So, if you run

Yes I am really sure hence the bug report. NO I am not tryng to run a second time. My testing was more carefull. I tested using 2 PC. I ran freshclam mannually and downloaded and noted version. On the test PC I would only run feshclam when I noted a version change. In every instance, where there was a vrsion change without TCP 3310 being opened to WAN the error was apparent. No I dont run freshclam manually at anymore after testing. I let it run for itself as set as a running service along with clamd. The system can do all the hard work - thats what is for ;-) cheers and thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=223772 alpha096@tpg.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|alpha096@tpg.com.au | ------- Comment #7 from alpha096@tpg.com.au 2006-11-30 14:44 MST ------- The reference was to clam 0.7 that since then there has been a GUI interface. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.