[jp] Sync problems - killing jpilot-sync

  • Previous message: [jp] Sync problems - killing jpilot-sync
  • Next message: [jp] Sync problems - killing jpilot-sync
  • Jason Day jasonday at worldnet.att.net
    Fri Dec 8 11:15:36 EST 2006

     

    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
    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.
    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.
    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.
    
    > 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.
    
    HTH,
    Jason
    -- 
    Jason Day                                       jasonday at
    http://jasonday.home.att.net                    worldnet dot att dot net
     
    "Of course I'm paranoid, everyone is trying to kill me."
        -- Weyoun-6, Star Trek: Deep Space 9
    
    

     

     

    More information about the jpilot mailing list