Mail Archives: cygwin/2004/11/12/12:43:21
On Fri, Nov 12, 2004 at 07:32:40PM +0200, Kamen TOMOV wrote:
>
> It's for sure that there are some things that are not quite clear, but
> in a nutshell:
>
> 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.
You have not provided the information requested in
http://cygwin.com/problems.html, despite being asked.
FWIW, what you describe would make sense if you are logged in under
Terminal Services and you do not have the Create Global Name privilege.
Pierre
--
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 -