Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 6 subscribers
  • Views 886 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

Sophos delays startup of DeltaWalker app for several minutes

jhencken

I've been using an excellent synchronizer product called DeltaWalker.  It works great but I had complaints about the startup time, which could last as long as five minutes.  Their support guy suggested my AV might be slowing down the startup because there's a lot of Java stuff in the app bundle which the AV would check every time I start the program.  So I checked it out.  If I temporarily disable Sophos scanning, DeltaWalker starts up instantly.

However, putting deltawalker.app in the Exclude from Scan list in Sophos did not help the problem.  I'd assumed that if the app is excluded, all the items in all the subfolders in the app bundle would be excluded.  Either that's not true, or Sophos is doing something else that's messing with DW's startup.  And Sopos does not give the option of selecting items that Finder locates inside app bundles, to put on the Exclude from Scan list.

Does anyone have any ideas for a fix/workaround for this?  I'd be very greatful for any assistance.

:1008177


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

    The easiest fix is to disable archive scanning in the on-access scanner -- this will disable scanning deep inside jar files.

    Excluding the app itself won't do much, as the cache files will still be scanned, ant the app will pump all the java code into the cache when you run it.

    Of course, the other issue is that the software is also likely doing lots of filie accessing as it runs -- and for every file access, Sophos will jump in and examine the file before letting DeltaWalker handle it.  So in essence, you're running up against both of the major pitfalls of using a complete on-access scan package when running DeltaWalker.

    Try it with archive scanning disabled to start with though; this may be all the fix you need (you just need to remember to do a scheduled disk scan from time to time to pick up anything that may be hiding in an archive file).

    :1008287
Reply
  • 0

    The easiest fix is to disable archive scanning in the on-access scanner -- this will disable scanning deep inside jar files.

    Excluding the app itself won't do much, as the cache files will still be scanned, ant the app will pump all the java code into the cache when you run it.

    Of course, the other issue is that the software is also likely doing lots of filie accessing as it runs -- and for every file access, Sophos will jump in and examine the file before letting DeltaWalker handle it.  So in essence, you're running up against both of the major pitfalls of using a complete on-access scan package when running DeltaWalker.

    Try it with archive scanning disabled to start with though; this may be all the fix you need (you just need to remember to do a scheduled disk scan from time to time to pick up anything that may be hiding in an archive file).

    :1008287
Children
No Data