Project

General

Profile

[logo] 
 
Home
News
Activity
About/Contact
Major Tools
  Dinotrace
  Verilator
  Verilog-mode
  Verilog-Perl
Other Tools
  IPC::Locker
  Parallel::Forker
  Voneline
General Info
  Papers

Issue #113

pidwatch issue on cygwin-thread-multi-64int

Added by Wilson Snyder almost 13 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
% Done:

0%


Description

This bug was cloned from Perl-RT, rt27140.

Email addresses have have been truncated.

Id:   27140
Status:        resolved
Queue:         IPC-Locker
Severity:    Important
Broken in:     1.470
Requestors:    RYBSKEJ <RYBSKEJ@>

Created:    Tue May 15 13:21:54 2007
Last Contact:     Sun Feb 08 09:09:23 2009
Closed:     Sun Feb 08 09:09:23 2009
Updated:     Sun Feb 08 09:09:23 2009 by WSNYDER
Tue May 15 13:21:57 2007 RYBSKEJ - Ticket created
Subject:  pidwatch issue on cygwin-thread-multi-64int
This issue is reported as an error in t/20-pidstat.t on
cygwin-thread-multi-64int, as shown at the end of this report. It
appears that the pidstat script is encountering some sort of issue with
the server that is preventing it from executing the remote command.

When I manually run the PidServer on port 66666, and then run the
command-line tool by itself, like:

perl -Iblib/arch -Iblib/lib script/pidwatch --port 12345 --pid 10 "echo
hello" 

I get the following response:

Hangup

The details of t/20-pidstat.t are as follows:

$ perl -Mlib=blib/lib,blib/arch t/20_pidstat.t
1..14
# Running under perl version 5.008007 for cygwin
# Current time local: Tue May 15 13:16:40 2007
# Current time GMT: Tue May 15 17:16:40 2007
# Using Test.pm version 1.25
ok 1
IPC::PidStat VERSION 1.470
ok 2
ok 3
ok 4
ok 5
Got response EXIS 1234 0 localhost
Pid 1234 Exists on localhost? 0
ok 6
Got response EXIS 66666 0 localhost
Pid 66666 Exists on localhost? 0
ok 7
Got response EXIS 3932 1 localhost
Pid 3932 Exists on localhost? 1
ok 8
ok 9
pidwatch ok:
returns:
ok 10
not ok 11
# Failed test 11 in t/20_pidstat.t at line 76
# t/20_pidstat.t line 76 is: ok($rtn eq "hello");
pidwatch fail:
returns:
ok 12
pidwatch immediate exit:
returns:
ok 13
check_pidstat:
ok 14 # skip nagios not installed (harmless)
Tue May 15 13:31:05 2007 WSNYDER - Correspondence added
> perl -Iblib/arch -Iblib/lib script/pidwatch --port 12345 --pid 10
"echo hello" 

This assumes your server is on port 12345, and there's a process ID 10
that exists (or not.)

So with the server on 12345 the correct answers are:

$ perl -Iblib/arch -Iblib/lib script/pidwatch --port 12345 --pid 1 "echo
hello" 
hello

$ perl -Iblib/arch -Iblib/lib script/pidwatch --port 12345 --pid 99991
"echo hello" 
Hangup (as there's no pid 99991.)

You may want to add a print of the command being executed to the test so
you can try it yourself. I'll add that to the next version.

Tue May 15 13:31:08 2007 RT_System - Status changed from 'new' to 'open'

Wed Jun 13 12:39:25 2007 WSNYDER - Correspondence added
Are you still having problems? If not I would like to close this issue.

Wed Jun 13 12:39:52 2007 WSNYDER - Status changed from 'open' to 'stalled'

Sun Feb 08 09:09:22 2009 WSNYDER - Correspondence added
No response.

Sun Feb 08 09:09:23 2009 RT_System - Status changed from 'stalled' to 'open'

Sun Feb 08 09:09:23 2009 WSNYDER - Status changed from 'open' to 'resolved'

Also available in: Atom