Mail Archives: cygwin/2004/11/12/13:13:00
> -----Original Message-----
> From: cygwin-owner On Behalf Of Kamen TOMOV
> Sent: 12 November 2004 17:33
> We have a daemon compiled with cygwin's fork, kill, etc.
>
> 1st scenario:
>
> - the daemon gets started as a Windows service
> - the daemon forks (calling the cygwin's version of fork()) and as a
> result we have a few children.
>
> The facts:
>
> - neither the daemon, nor its children are seen by cygwins's ps.exe or
> could be killed with kill.exe, or kill().
>
> - calling cygwin_winpid_to_pid on the parent's pid or any of its
> children's pid returns the error result: -1.
>
> 2nd scenario:
>
> - the daemon gets started from the bash's command line.
>
> The facts:
>
> - the daemon is seen in the list of processes given by ps.exe and
> could be killed with kill.exe.
Ok, well if it isn't the terminal server thing, it's probably still perms.
Administrator has lower privs than SYSTEM, so can't necessarily kill SYSTEM
tasks (depending on ACL etc).
Try the 1st scenario (daemon as service), then fire up a sysbash shell, and
see if you can ps/kill the children from that. If it works, you'll know its
perms.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -