D
Darryl
I have two questions about services.
Why is it that the SMTP, IIS Admin, and WWW service all start the same
inetinfo.exe executable, without parameters? How can this accomplish
3 different functions with only 1 executable?
Also, I'd swear that even when our services are set to restart/recover
upon failure, none of them ever do. I have one services (AutoExNT)
that starts a CMD window & is set to interact with the desktop, so I
should SEE the window when it restarts, but it never does. It fails
the first time because it is dependant on the WWW service. The WWW
service is slow to start & reports that it hung on starting, although
I can browse just fine and it says "started". But once the WWW is up,
the AutoExNT never restarts, even though it is set to do so. I can
manually request a restart just fine.
Why is it that the SMTP, IIS Admin, and WWW service all start the same
inetinfo.exe executable, without parameters? How can this accomplish
3 different functions with only 1 executable?
Also, I'd swear that even when our services are set to restart/recover
upon failure, none of them ever do. I have one services (AutoExNT)
that starts a CMD window & is set to interact with the desktop, so I
should SEE the window when it restarts, but it never does. It fails
the first time because it is dependant on the WWW service. The WWW
service is slow to start & reports that it hung on starting, although
I can browse just fine and it says "started". But once the WWW is up,
the AutoExNT never restarts, even though it is set to do so. I can
manually request a restart just fine.