T
Tim Gorgs
Hi all, first a short description of my problem:
On a few houndred systems (W2000 / WXP) we have a selfwritten
system-service installed which most of the time does nothing than to
wait for commands over TCP-IP on a certain port to start an
application. On almost all of these systems the service ran well, and
there were no problems (so far)...
Now on two Windows XP systems the problem appeared that the
svchost.exe started (not always reproducable) to create a lot of
cpu-usage (about 70%). When my colleagues stopped my service, the
cpu-usage went back to about zero.
My question now is, if our service has something to do with the
problem. As the Microsoft documentation says, svchost.exe is only for
services, which are being executed from a *DLL*, but our service is a
standalone EXE.
When I go through the output of "tasklist /svc" none of the
svchost.exe entries shows our servicename, as it's listed seperately.
The whole behaviour seems to be very strange, because on the one hand
I would think, that our service causes the problem (disabling it
reduces the svchost.exe), on the other hand our service doesn't show
up under the svchost but as a seperate entry in the taskmanager (and
the service-EXE's cpu-usage is always zero)
Any help is greatly appreciated, perhaps someone can give me some
hints or at least clearify if our service can be responsible for the
cpu-usage or not (does it affect the svchost in any way, even though
it's a standalone EXE???)!
Thank you very much
Tim
On a few houndred systems (W2000 / WXP) we have a selfwritten
system-service installed which most of the time does nothing than to
wait for commands over TCP-IP on a certain port to start an
application. On almost all of these systems the service ran well, and
there were no problems (so far)...
Now on two Windows XP systems the problem appeared that the
svchost.exe started (not always reproducable) to create a lot of
cpu-usage (about 70%). When my colleagues stopped my service, the
cpu-usage went back to about zero.
My question now is, if our service has something to do with the
problem. As the Microsoft documentation says, svchost.exe is only for
services, which are being executed from a *DLL*, but our service is a
standalone EXE.
When I go through the output of "tasklist /svc" none of the
svchost.exe entries shows our servicename, as it's listed seperately.
The whole behaviour seems to be very strange, because on the one hand
I would think, that our service causes the problem (disabling it
reduces the svchost.exe), on the other hand our service doesn't show
up under the svchost but as a seperate entry in the taskmanager (and
the service-EXE's cpu-usage is always zero)
Any help is greatly appreciated, perhaps someone can give me some
hints or at least clearify if our service can be responsible for the
cpu-usage or not (does it affect the svchost in any way, even though
it's a standalone EXE???)!
Thank you very much
Tim