Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 3681 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Additional scanning thread messages on Linux systems since updating

Phaethar

Hey all,

We pushed out Sophos version 9 via Enterprise Console earlier in the week, and since then we've been seeing a lot of messages showing up on the system messages logs that look like this:

savscand.control.log: [en]Additional scanning thread has been started

savscand.control.log: [en]Additional scanning thread has been stopped

I'm trying to find out what the cause is of these messages. They show up at different times for different systems. They are not logged as errors, and Enterprise Console does not show them as errors, or as a problem of any kind. Is there some way I can find out what it's scanning? Is something failing, or are these just informative messages? If so, what are they doing?

They are showing up a lot in our daily log reviews, and I'd like to have an explanation as to what they mean.

The Linux servers are running a mix of CentOS 5 and 6, with a few RHEL 5 systems in there as well.

Thanks!

:39337


This thread was automatically locked due to age.
Parents
  • 0

    They are messages from the adaptive thread function added in Sophos Anti-Virus for Linux 9:

    The first message means a savscand started an additional scanning thread as all existing scanners where busy and there were outstanding scan requests the last two times it measured the queue length.

    The second message means the savscand stopped the additional scanning thread as the queue was empty the last two times it measured the queue length.

    Each savscand measures the queue about every 2 seconds.

    :39343
Reply
  • 0

    They are messages from the adaptive thread function added in Sophos Anti-Virus for Linux 9:

    The first message means a savscand started an additional scanning thread as all existing scanners where busy and there were outstanding scan requests the last two times it measured the queue length.

    The second message means the savscand stopped the additional scanning thread as the queue was empty the last two times it measured the queue length.

    Each savscand measures the queue about every 2 seconds.

    :39343
Children
No Data