ECTED]
Sent: Thursday, 23 June 2005 4:18 AM
To: cygwin@cygwin.com
Subject: Re: Problem installing CPAN module
Sonam Chauhan wrote:
> Hi - While doing a fresh install of Cygwin, I have run into errors
> installing a CPAN Perl module that worked last month. The module is
> Proc::ProcessTab
Hi - While doing a fresh install of Cygwin, I have run into errors
installing a CPAN Perl module that worked last month. The module is
Proc::ProcessTable. It now reports a "`PID_ZOMBIE' undeclared" error message
during compilation. The relevant snippet is below.
Back in May, I reported a differen
r CW_... query that would report on PIDs
> >accurately?
>
> CW_GETPINFO reports on PIDs accurately, AFAIK.
Thanks.
Cheers,
Sonam Chauhan
--
Electronic Commerce, Corporate Express Australia Ltd.
Phone: +61-2-9335-0725, Email: [EMAIL PROTECTED]
--
Unsubscribe info: http://cygwin.c
Chris:
> >> >ps -W will also not always properly report on execed processes in
> >> ^
> >> >general. Since ps -W uses CW_GETPINFO_FULL,
...
> >Won't it be better fixing this bug, than fixing 'Proc::ProcessTable' and
> > 'ps -W' and all
... by implication, CW_GETPINFO_FULL does not report on execed processes
properly.
If this is the case, isn't this a bug in CW_GETPINFO_FULL?
Won't it be better fixing this bug, than fixing 'Proc::ProcessTable' and 'ps
-W' and all the other programs that uses CW_GETPINFO_FULL?
erl processes -- reported normally.
2. PID and PPID of the 'sleep' process -- reported as if it was a non-Cygwin
process. i.e. PID=, PPID=0.
But the 'sleep' process is a "Cygwin process", right?
Does this indicate a bug in CW_GETPINFO_FULL?
Regards,
Son
tivePerl's kill wouldn't use signals at all, so that part of the
discussion went the wrong way. Sorry for the confusion from my side.
In another email you said:
> As I understand it, kill -9 does not send a signal, and certainly not to a
> windows program.
That's interesting
alc &
[1] 2380
$ ps -W | grep calc
238037802380 36040 400 15:18:21
/cygdrive/c/WINDOWS/system32/calc
3604 0 0 3604?0 15:18:22
c:\WINDOWS\system32\calc.exe
===
Regards,
Sonam Chauhan
--
Electronic Commerce,
Reini:
[Note, I'm no Cygwin expert, so please correct any misunderstandings.]
> >>or fix it in this module XS. It's really easy with the cygwin provided
> >>translation functions.
> >> See http://sourceware.org/ml/cygwin/2005-02/msg00154.html
...
> > After all, Proc::ProcessTable misreports the
adding
functionality for looking up the WINPID from the Cygwin process ID? Is the
fix really that simple? After all, Proc::ProcessTable misreports the PID and
PPID only under certain conditions -- this would indicate a complex issue in
Proc::ProcessTable XS code, right?
Regards,
Sonam Chauhan
--
s make sense.
So, a good reason to test is Cygwin's handling of 'ls //' has changed - from
listing the root directory, to listing servers in the workgroup/domain.
Regards,
Sonam Chauhan
--
Electronic Commerce, Corporate Express Australia Ltd.
Phone: +61-2-9335-0725, Email: [EMAIL P
/etc
4. ls etc
(*) On Cygwin, command #2 returns:
-
$ ls //etc
ls: //etc: No such file or directory
-----
Regards,
Sonam Chauhan
--
Electronic Commerce, Corporate Express Australia Ltd.
Phone: +61-2-9335-0725, Email: [EMAIL PROTECTED]
-
windows programs.
What is 'AIUIkill'? Did you mean 'kill -9'? Isn't SIGKILL a Unix signal? The
context of the original discussion was about killing processes by sending a
SIGKILL (please see: http://sourceware.org/ml/cygwin/2005-05/msg00550.html )
Sincerely,
Sonam Chauha
ss you wrote the Perl XS interface for
Proc::ProcessTable (or something similar that controls it's behavior), this
does not concern your code which probably behaves just fine.
Coming back to actual issue I referenced a discussion earlier on this
list where a similar problem was discussed
Christopher -
> Yes, if you send a "kill -9" to a pid that shows up in ps but is
> associated with a non-cygwin process, it should work.
So what me and Jurgen were discussing works, and you were wrong. Thanks for
revisiting your point after your earlier rudeness.
Regard
ioned:
> ActiveState perl is a windows program. You can't send cygwin (aka unix)
> signals to a windows proram.
This should be possible if the ActiPerl Windows executable was executed from
a Cygwin terminal -- 'ps' shows it running and 'kill -9' should kill it.
Regards,
S
s
the following package status for cygwin and Perl:
--
cygwin 1.5.16-1 OK
perl5.8.6-4OK
------
Can anyone help?
Regards,
Sonam Chauhan
--
Electronic Commerce, Corporate Express Australia Ltd.
Phone: +61-2-9335-0725, Email: [EMAIL PROTECTE
17 matches
Mail list logo
