Re: Changes to calendar objects reg. alarms.



On Tue, 28 Dec 1999, Miguel de Icaza wrote:

> This is very strange Eskil.  Because, the GnomeCal is not running into
> the same address space as the conduit is, right?

The problem is in both, the conduit shares .c files with gnomecal, and
alarm.c calls setitimer. In addition to that, corba-cal.c methods also
cause additional setitimer calls. 

So after sync, both gpilotd and gnomecal have called setitimer more then
they want to. Gpilotd gets the false sigalarms and gnomecal gets multiple
for each event.

/dev/eskil
---




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]