Re: [clamav-users] Trying to track down bug using lsof & clamscan/clamdscan.. odd behavior

2015-08-28 Thread Shawn Webb
On Thursday, 27 August 2015 01:48:00 PM Charles Swiger wrote: > On Aug 27, 2015, at 1:13 PM, Alexander Urcioli wrote: > > We were running into an issue where larger files were not able to be moved > > after scanning with ClamAV. Our hypothesis was that perhaps the process > > has > > not released

Re: [clamav-users] Trying to track down bug using lsof & clamscan/clamdscan.. odd behavior

2015-08-28 Thread Alexander Urcioli
I'm happy to report we located the bug which was not at all due to clamav. However knowledge gained! Thanks everyone. On Fri, Aug 28, 2015, 12:31 Shawn Webb wrote: > On Thursday, 27 August 2015 01:48:00 PM Charles Swiger wrote: > > On Aug 27, 2015, at 1:13 PM, Alexander Urcioli > wrote: > > > W

Re: [clamav-users] Trying to track down bug using lsof & clamscan/clamdscan.. odd behavior

2015-08-28 Thread Shawn Webb
Would it be possible to share that knowledge so that others who may have the same experience can draw from yours? On Friday, 28 August 2015 05:22:16 PM Alexander Urcioli wrote: > I'm happy to report we located the bug which was not at all due to clamav. > However knowledge gained! Thanks everyone

Re: [clamav-users] Trying to track down bug using lsof & clamscan/clamdscan.. odd behavior

2015-08-28 Thread Alexander Urcioli
Sure, its not really relevant to ClamAV which is why I omitted it but basically the logic in our node application was incorrect so we were returning a status before the stream was closed which was causing our problem. On Fri, Aug 28, 2015 at 1:25 PM, Shawn Webb wrote: > Would it be possible to s