RE: Problem with syncing/connecting to gpilotd

["Manuel A. McLure" <mmt unify com>]

I knew it was my fault! How dare I use a real pilot instead of xpilot! :-)

Seriously, I'm glad you could reproduce it - hopefully it's something small
and easy to fix. Unfortunately I don't know enough GNOME/ORBit to be able to
help. What throws me is that the daemon is getting a SIGINT from seemingly
nowhere. Is it possible that it's failing to fork and killing itself instead
of killing the child, or that the child is dying and the SIGCLD is being
interpreted as a SIGINT?

--
Manuel A. McLure - Unify Corp. Technical Support <mmt@unify.com>
Vah! Denuone Latine loquebar? Me ineptum. Interdum modo elabitur.


-----Original Message-----
From: Eskil Heyn Olsen [mailto:deity@dbc.dk]
Sent: Wednesday, January 05, 2000 2:21 PM
To: Manuel A. McLure
Cc: 'gnome-pilot-list@gnome.org'
Subject: RE: Problem with syncing/connecting to gpilotd


On Wed, 5 Jan 2000, Manuel A. McLure wrote:

> The sigint occurs immediately every time I hit the sync button on the
> cradle, IF (and only if) the gpilotd was started as a corba server (i.e.,

Dude, you're right. I can now reproduce it. As for the extra specialities,
it only sigints when using a real pilot, not xcopilot.

Okaeh, I'm going to use some time on this bugger.

/dev/eskil
---