IIS 6.0 Automatic Restart

Kristofer has explained what is going on.

Basically, every time a worker process opens a log file handle, it will
write the log headers into it. Worker process opens a log handle when it is
starting up. Things that cause worker process to recycle (and hence forced
to start up again to handle a future request) include:
1. Recycling based on health-monitoring metrics, such as idle-timeout,
#-request, time-period, CPU usage, memory usage, etc
2. Some other code in the process crashed
3. Someone stops IIS or runs a tool like IISRESET (which stops/restarts IIS)


So, to answer your question
1. IIS doesn't "reset itself". IIS normally recycles worker processes,
which does not reset IIS. Only if someone explicitly ran IISRESET, stopped
IIS, or crashed IIS (highly unlikely in worker process isolation mode) does
IIS "reset"
2. When w3wp starts up again, to handle a request, AFTER a process recycle,
do you see new log headers.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"tmeister" <tmeister RemoveThis @discussions.microsoft.com> wrote in message
news:10E676CB-1906-4BA8-8CD0-D1491E7740EC@microsoft.com...
I have a hosting company hosting one of my sites. I noticed in the IIS Log
files that there were over 20 restarts that ocurred during the day. There
were 20 times that the log file headers appeared which I think happen after
an IISReset. When I asked the hosting company about this they indicated
that
"it was just iis reseting itself as it is designed to do". I wasn't aware
that IIS was supposed to reset itself. I understand that under IIS 6.0 that
the worker process will recyle itself but I did not think it did an
IISReset.

I guess my questions are 1) Is the hosting company correct when they say
that IIS resets itself? and 2) when a process is recycled do the headers
show up in the IIS Log files?

Thanks
 >> Stay informed about: IIS 6.0 Automatic Restart