Re: [sisyphus] licq & vicq

[Vladimir Alyekhin <flea@mailru.com>]

Hi Artem!
On Thu, Nov 28, 2002 at 02:20:38PM +0300, you wrote:
> Доброго времени суток!
> 1. Заметил после обновления perl до 5.8, что vicq теперь говорит о том, что
>    пришло сообщение не сразу, а после ввода строки с клавиатуры
=cut

  From: Alexander Timoshenko <gonzo@ukrweb.net>
  To: vicq-devel@expo.ukrweb.net
  Subject: Re: [vicq-devel] vicq delayed message display (new perl??)
  Date: Sat, 31 Aug 2002 16:52:49 +0300

The Black Unicorn (tbu@pandora.be) wrote:
> Hi,
> 
> I've been using vicq for quite a while (the one in the debian testing
> distro : vicq 0.4.1-2, library 0.04-2) It's always worked nicely.
> 
> Since my last dist upgrade, however, it doesn't display incoming
> messages, white paper info etc, when it comes in. Instead, it displays
> them only after I've executed another command (usually 'e' :))
> 
> In other words, I need to 'trigger' vicq into displaying pending info
> each time. Obviously, this is nowhere near useful.
> 
> I've also tried the latest development version, and it didn't help
> 
> One of the major changes in my last debian upgrade was the upgrade from
> perl to perl 5.8.0-10. A friend of mine who has kept the perl upgrade on
> hold, doesn't have the problem.
> 
> A ny idea on how to solve this ?
        Thats because of new feature of perl5.8.0  - async signals. SIGALARM
delivers to vicq only _after_ I/O operation(readline() in our case) complete.
The only fix for now downgrade perl to 5.6.0. May be a bit later i'll
try to deal with 5.8.0  :-/

=cut

-- 
Vladimir Alyekhin
CJSC "Internet-Service"
VA2-UANIC