I'm upgrading an ancient (2004-era) server to the modern era:
2.6.18-92.1.6.el5 x86_64 x86_64 x86_64 GNU/Linux
Perl 5.10
Event.pm 1.1
One of my applications throws the following error once it's been running for a
few minutes as a daemon:
Assertion (((pe_watcher*)wa)->flags & 0x0008) || !wa->runn
s fd. The problem is that my callback
is getting invoked over and over, even though there's only one NOTIFY
being sent. (I'm issuing the NOTIFY from a SQL prompt.)
Do I have to do something to clear the event after I process it? I've tried issuing a
sysread() against the fd,
gure('Event::idle=HASH(0x8235400)') called at
testevent.pl line 16
The problem lies in the while() loop, as it can't end without trying to
reference part of the array that doesn't exist.
I have a dim memory that splice() used to silently ignore references to
negative subscripts
think that
while (my ($k,$v)= splice @_, -2) { $o->$k($v)}
is a bug that should read
while (@_ and my ($k,$v)= splice @_, -2) { $o->$k($v)}
at least, under perl 5.6.1.
--
Jeff Boes vox 616.226.9550
Database Engineer
What is the significance of these messages?
Event: multiplex 0.0060s at ...
I can't find anything on them in the code or docs.
--
Jeff Boes vox 616.226.9550
Database Engineer fax 616.349.9076
Nexcerpt
=> 'r',
);
I don't seem to get any events on this socket.
--
Jeff Boes vox 616.226.9550
Database Engineer fax 616.349.9076
Nexcerpt, Inc. [EMAIL PROTECTED]
The
other never gets called.
--
Jeff Boes vox 616.226.9550
Database Engineer fax 616.349.9076
Nexcerpt, Inc. [EMAIL PROTECTED]
On Wed, 22 Aug 2001 04:01:29 +0200
<[EMAIL PROTECTED] ( Marc) (A.) (Lehmann )> wrote:
> On Thu, Aug 16, 2001 at 02:16:58PM -0400, Jeff Boes <[EMAIL PROTECTED]> wrote:
> > I've got two timer events with the same interval but different callbacks.
> > One of them
. Obviously, I could set it at the bottom of every routine.)
--
Jeff Boes vox 616.226.9550
Database Engineer fax 616.349.9076
Nexcerpt, Inc. [EMAIL PROTECTED]
I understand that. I use Event->timer and Event-idle elsewhere.
What I'm wondering is whether Event->io does anything differently if you
supply min and max versus if they are omitted.
--
Jeff Boes vox 616.226.9550 ext 24
Database E
What might these messages mean?
Event: 'NEW_JOB_INDEX' was unexpectedly closed at
/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Event.pm line 148
These started after I added Cache::Cache modules to a working program
that uses Event.
--
Jeff Boes
poll => 'r',
max => TIMEOUT_PERIOD,
);
but I'm not sure I'm on the right track.
--
Jeff Boes vox 269.226.9550 ext 24
Database Engineer
most
time.
--
Jeff Boes vox 269.226.9550 ext 24
Database Engineer fax 269.349.9076
Nexcerpt, Inc. http://www.nexcerpt.com
...Nexcerpt... Extend your Expertise
doc
correctly.) And how can it (the event handler) unqueue the pending
events for itself? Just "$watcher->stop and $watcher->start"? Does
this have side effects that I need to check for?
--
Jeff Boes vox 269.226.9550 ext 24
Datab
event has a higher priority than '0', or
that events inserted via now() always outrank pre-existing events.
--
Jeff Boes vox 269.226.9550 ext 24
Database Engineer fax 269.349.9076
Nexcerpt, Inc.
any "gotchas" I should watch for? I've not made any attempt
previously to alter the Event.pm code.
--
Jeff Boes vox 269.226.9550 ext 24
Database Engineer fax 269.349.9076
Nexcerpt, Inc.
ady-to-go when Event::loop is called. I tried
$event->w->now();
Event::loop();
but that doesn't seem to do it either. Do I need to create a separate
event like this?
my $one_shot =
Event->timer( after => 0,
cb=> $main_loop,
);
On Thu, 2003-06-12 at 16:04, Jeff Boes wrote:
> ready-to-go when Event::loop is called. I tried
>
> $event->w->now();
> Event::loop();
>
> but that doesn't seem to do it either.
Oops, it does do it. Never mind ...
--
Jeff Boes
ever repeats (the
reported wake-up time is some 90 seconds in the future).
--
Jeff Boes Vox 269-226-9550 x24
Director of Software Development Fax 269-349-9076
Exfacto! Exceptional Online Content http://www.exfacto.com
N
then by doing --
$e->stop;
$e->at(time + $next);
$e->start;
I dunno why the "stop" call is necessary, but the event won't fire a
second time without it!
--
Jeff Boes Vox 269-226-9550 x24
Director of Software Development
20 matches
Mail list logo