Re: Why sync for each conduit setting?

[Vadim Strizhevsky <vadim optonline net>]

Dan Hensley writes:
 > Eskil Heyn Olsen wrote:
 > 
 > > On Fri, 14 Jan 2000, Dan Hensley wrote:
 > >
 > > > > > This is really annoying.  Why do I have hit the synch buitton everytime
 > > > > > I switch conduit windows in gnome-help?
 > > > > You mean gnomecc, not gnome-help ? Press the synch button ? You shouldn't.
 > > > > The only capplet that interacts with the pilot is pilot-link. What excatly
 > > > > are you doing ?
 > > > The one time I did get my pilot to sync (by the way, I have a Palm IIIe, in
 > > > case that makes any difference), I saw exactly the same thing.
 > >
 > > Dudes, this isn't helping me much ; You saw what ? You where doing what ?
 > > Which windows ? The synch button on the cradle ?
 > 
 > Since I can't even get it to sync now, I won't be able to provide many details,
 > but here's what I remember:
 > Set up Pilot Link.  Hotsync (cradle).  Everything copies from pilot into
 > $HOME/pilot.  Then go to a conduit setting in gnomecc (doesn't matter which
 > one).  Nothing shows up.  Hit the Hotsync button (cradle).  The dialog shows up.
 > Change settings on the dialog and hit OK.  Here's where I can't remember if I
 > need to hit Hotsync here.  Select either the same or another conduit setting.
 > Nothing shows up.  Hit the Hotsync button (cradle).  Dialog shows up.  (etc.)

This very suspiciously sounds to me like gpilotd is eroneously waking up
and then hanging in pi_accept. This might be fixed by a commit I did
last night, because I was seeing this sometimes too, but only when I
switch between different usages of the serial port. Do you by any
chance do that too? And you don't have any other programs/deamons
trying to listen on the same serial port at the same time, do you?

-Vadim