From the error message and the common symptoms, I'd guess that
PBS_POSTBACK is going out of bounds somewhere or $old_info is not
pointing to an array that is fully initialized correctly.
That is just a guess, though.
-jeff
At 12:00 PM 10/7/2007, you wrote:
Actually, I'm chasing the exact sa
Actually, I'm chasing the exact same problem right now. I think either my
ping volume or frequency dramatically dwarfs yours, because I can trigger
a consistent failure within a few hours. =)
- billn
On Sun, 7 Oct 2007, William Fletcher wrote:
> Hi,
>
> Not too sure if this is mildly off top
Hi,
Not too sure if this is mildly off topic, so please let me know if it is...
I have a piece of software using POE's Ping.pm component, etc...
It is essentially a daemon.
It works for about 10-15 days before it dies with this the following:
Use of uninitialized value in subroutine entry at
. post()ed and I/O events are due to be dispatched at
Time::HiRes::time(), effectively making them FIFO.
By posting all your requests at once, you've delayed any I/O events
until after all the requests can be received by
POE::Component::Client::Ping.
The component sends the first $pa
Hello-
Two items/questions regarding Client::Ping;
1) Client::Ping payload option?
Would a patch for Client::Ping be considered that would allow a user to
set their own data pattern?
my $datapattern = delete $params{DataPattern};
$datapattern = 'Use POE!' x 7 unless defined $datapattern
...
$hea
On Tue, May 30, 2006 at 03:17:20PM +0100, Nigel Bowden wrote:
>
> Anyone got any pointers on this, or is there maybe an issue in this area ?
>
Hi,
It appears that the passing of user data in PoCo-Client-Ping 'broke' with the
release of 1.10.
With 1.04 it works fine.
I have reported this to Ro
Hi,
I'm using POE::Component::Client::Ping (1.11), and I'm having difficulty
passing user data from as ping as per the documentation :
use POE::Component::Client::Ping ":const";
# Post an array ref as the callback to get data back to you
$kernel->post("pinger&qu
caused the state
> to be
> > > called. Under certain network conditoins, packets may come back out of
> > > order, and I need to know what order they arrived in. The request time
> isn't
> > > precise enough to tell.
> > > Any ideas?
> >
> >
to be
> > called. Under certain network conditoins, packets may come back out of
> > order, and I need to know what order they arrived in. The request time
isn't
> > precise enough to tell.
> > Any ideas?
>
> Please ignore my previous message. The SYNOPSIS code I
s, packets may come back out of
> > order, and I need to know what order they arrived in. The request time
isn't
> > precise enough to tell.
> > Any ideas?
>
> Please ignore my previous message. The SYNOPSIS code I copied has
> errors. A new POE::Component::Client::P
enough to tell.
> Any ideas?
Please ignore my previous message. The SYNOPSIS code I copied has
errors. A new POE::Component::Client::Ping with better documentation
is on its way to the CPAN.
Meanwhile...
A single session cannot request multiple pings for the same address at
the same time
enough to tell.
> Any ideas?
Replace the response event with an arrayref. The first item in the
arrayref should be the response event; the remaining items are "magic
cookie" or other context data you send through the component.
>From the SYNOPSIS:
use POE::Component::Client::Pin
Hi all,
Is it possible to pass information between states using
POE::Component::Clinet::Ping?
What I'm trying to do is ping the same target 5 times in succession, and
then see if all pings come back in the same order as they left. I need to be
able to tell, in the got_pong state, which packet has
Hello POE people:
On debian sid with perl 5.6.1:
Checking if your kit is complete...
Looks good
Writing Makefile for POE::Component::Client::Ping
cp Ping.pm blib/lib/POE/Component/Client/Ping.pm
Manifying blib/man3/POE::Component::Client::Ping.3
/usr/bin/make -- OK
Running make test
14 matches
Mail list logo
