Avast WEBforum
Consumer Products => Avast Mac Security => Topic started by: Uh_Clem on July 12, 2012, 02:57:36 AM
-
I noticed that Ovidiu had posted a similar question in April but, since there were no replies, I'm going to present my issue.
Although all appears to be working properly, avast! is cranking out an error message in the avastfileshield.log at irregular intervals. A partial listing of my log reads:
[895-err] Wed Jul 11 14:56:30 2012 - kext_setsockopt: setsockopt failed. Operation not supported [45]
[895-err] Wed Jul 11 15:02:22 2012 - kext_setsockopt: setsockopt failed. Operation not supported [45]
[895-err] Wed Jul 11 15:14:29 2012 - kext_setsockopt: setsockopt failed. Operation not supported [45]
[895-err] Wed Jul 11 15:22:12 2012 - kext_setsockopt: setsockopt failed. Operation not supported [45]
[895-err] Wed Jul 11 15:22:13 2012 - kext_setsockopt: setsockopt failed. Operation not supported [45]
[895-err] Wed Jul 11 15:22:13 2012 - kext_setsockopt: setsockopt failed. Operation not supported [45]
[895-err] Wed Jul 11 15:22:14 2012 - kext_setsockopt: setsockopt failed. Operation not supported [45]
[895-err] Wed Jul 11 16:48:55 2012 - kext_setsockopt: setsockopt failed. Operation not supported [45]
[895-err] Wed Jul 11 16:48:57 2012 - kext_setsockopt: setsockopt failed. Operation not supported [45]
[895-err] Wed Jul 11 16:48:58 2012 - kext_setsockopt: setsockopt failed. Operation not supported [45]
[895-err] Wed Jul 11 16:48:59 2012 - kext_setsockopt: setsockopt failed. Operation not supported [45]
[895-err] Wed Jul 11 16:49:13 2012 - kext_setsockopt: setsockopt failed. Operation not supported [45]
[895-note] Wed Jul 11 17:04:29 2012 - Detected unmount of /Volumes/PC_USB
[Note that this is a truncated but unedited list. There were no intervening messages other than the ones shown.]
I haven't determined any particular action associated with the message. As you can see, it may go an hour or more without occurrence or appear four times in five seconds. Any ideas?
-
Thanks for the report.
I know about the setsockopt() problem. It is being worked on. For now, it is not pretty but it is unharmful.
About the unmount: the fileshield has a cache of on-access scan results to limit multiple scans of the same file. The results are removed when the file is modified, or also on unmount of filesystem they sit on, so that's just a note such an event happened.
Regards,
mity
-
Mity, thanks for the quick response. I had assumed the unmount message was purely informational (hence the [xxx-note ]msg code). I only included it as a boundary for the other messages.