Using the very latest Cooker packages (as of about 1900 hours GMT-5:00,
8 August), gpilotd exhibits repeatable crashes on my system. In
addition, the gpilotd started by default during my GNOME login does not
respond to hotsync inits started by pushing the hotsync button on the
cradle.
More detail (1): Using gpilot-install-file to install a PDB or PRC file
seems to work fine, the first time I try it. The second time, gpilotd
crashes immediately after I press the hotsync button. For me, at least,
this is consistently reproduceable, and does not seem to depend on any
particular PRC or PDB file. Any hotsyncs that do not involve
gpilot-install-file seem to work just fine. After gpilotd dies, I can
restart it and try again, and the transfer works fine. A second attempt
at installing a file with gpilot-install-file always fails, and kills
gpilotd.
More detail (2): When I log into the GNOME environment, gpilotd appears
to have been started with no switches. Pressing the hotsync button on
the cradle does not start a transfer. After killing gpilotd and
restarting, hotsyncs initiated from the cradle work fine.
I'm using an IBM Workpad C3 (a rebadged Palm Vx) running PalmOS 4.1.
It's in a serial hotsync cradle connected to /dev/ttyS0.
A further nitpick: during testing of the gpilot-install-file problem, I
accidentally managed to produce a corrupted PDB file. Attempting to
transfer this seems to kill gpilotd instantly -- it would be nice if
gpilotd were to abort the transfer and recover gracefully.
--
"However, Science People like to believe in laws, even when such laws
can be circumvented by their own Science. They become most displeased
if you suggest it would be more accurate to speak of the Generally
Good Idea of Gravity or the Three Useful Guidelines of
Thermodynamics."
-- James Alan Gardner, /Ascending/
