|
|
BITS DOES clean up the jobs that are not cleaned up by the applications 90
days after the job creation date. This parameter is configurable via group
policy. Please look at
http://msdn.microsoft.com/library/en-us/bits/bits/group_policies.asp
We would like to understand what do you mean by "nasty" effects. Can you
please give more details?
--
Narayana Mahankali
Microsoft, BITS
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
www.microsoft.com/info/cpyright.htm">http://www.microsoft.com/info/cpyright.htm
<ljwhitmire@xxxxxxxxx> wrote in message
news:1111286205.768822.240660@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Well, I hope this doesn't get posted twice, but anyway BITS does NOT
> clean up partially created jobs. I think it is suppose to timeout jobs
> that have been resumed, but not
> ones that are partial. Either way, we had an app that left 15k+ jobs on
> a test machine over several months. That number has nasty side effects
> on BITS! We now flush all old jobs from BITS when our service stops (at
> least the ones we created).
>
> -jaye
>
|
|