On Feb 20, 2012, at 17:44 , Preston Landers wrote:
> Offhand it sounds like a authorization related issue. Have you tried
> checking the current user identity / authorization from within the
> child processes?
That seems to be the problem. The service itself was registered to run under no
part
I guess it depends on what that child process does. Services run on a
different desktop, so any UI (eg, message box or similar) or attempts to
read from stdin etc will make it appear to have hung. Using a windows
debugger (or even "process explorer" from the MS SysInternals team)
might give y
Hi Preston,
> Offhand it sounds like a authorization related issue. Have you tried
> checking the current user identity / authorization from within the
> child processes?
Not yet. The service itself is run without specific credentials.
> Is there a reason you're calling CreateProcess directly
Hi all,
I've written a Windows service based on win32serviceutil.ServiceFramework. The
service per se is running just fine. I am testing it on Windows Server 2003.
When starting, the service uses the win32process.CreateProcess to start a
process:
win32process.CreateProcess(None, , None, None,
