Hi Jason! Jason Day wrote: > On Thu, Dec 07, 2006 at 04:03:17PM +0100, Eamann O Ruairc wrote: > >> root at eamann-laptop:/home/eamann# ps ax | grep pilot >> 15359 ? S 0:00 /bin/sh -c /usr/bin/jpilot-sync >> 15360 ? R 0:15 /usr/bin/jpilot-sync >> > > At what point did you execute this command? This looks like something > is automatically launching jpilot-sync, which will prevent you from > syncing with the jpilot GUI. Try this: > > 1) Exit jpilot > 2) Make sure jpilot-sync is not running by running the ps command above > jpilot-sync is not running > 3) If jpilot -sync is running, kill it by typing "kill <PID>", where > <PID> is the pid of the process returned by ps. Above, the <PID> would > be 15360. After you kill it, run the ps command again and make sure it > really is killed. > Just to make sure, I run the ps command a few times more > 4) Cradle your zire and hit the hotsync button > 5) Run the ps ax | grep pilot command a few more times > 6) Do you see jpilot-sync in the output? If so, then you've got a > hotplug or udev script launching it automatically. In that case, try > running this command (it may take a while): > grep -r jpilot-sync /etc > That *should* reveal what is starting jpilot-sync. > No mention of jpilot-sync in the output: root at eamann-laptop:/home/eamann# ps ax | grep pilot 11860 pts/0 R+ 0:00 grep pilot > 7) If you *did not* see jpilot-sync running, then try the install-user > command again. Make sure you hit the hotsync button on the cradle (or > your handheld) *first*, then run the install-user command. If > install-user says it cannot bind to the port, run it again immediately. > Keep trying until it connects, or your handheld says it was unable to > connect. > I ran the install-user command about ten times, but to no avail: root at eamann-laptop:/home/eamann# install-user -p /dev/pilot -u eamann -i 12345 Unable to bind to port: /dev/pilot Please use --help for more information >> When my syncing problems began I consulted the JP Users' Manual and read >> that it would be useful to make a link as in "ln -s /dev/ttyS0 >> /dev/pilot". Then I saw from /var/log that JPilot seemed to be using >> both ttyUSB0 and ttyUSB1, so, for good measure, I made a link to both. >> Could that be the origin of the two sync processes? If so, how do I undo >> a link? >> > > Delete the link with the rm command: rm /dev/pilot . Udev should create > the link for you. > I was unable to implement that command: root at eamann-laptop:/home/eamann# rm /dev/pilot rm: cannot remove `/dev/pilot': No such file or directory Thanks once again for your help! Eamann > HTH, > Jason >
More information about the jpilot mailing list