Thanks for the tip, Carlo, and sorry for not having answered sooner!
I did as you suggested and got the following:
root at eamann-laptop:/home/eamann# ps -e -o "pid ppid args" | grep jpilot-sync
8543 7444 grep jpilot-sync
root at eamann-laptop:/home/eamann# ps -e | grep 7444
7444 pts/1 00:00:00 bash
What can I deduce from that?
Eamann
Carlo Graziani wrote:
> A tip for figuring out who is responsible for starting jpilot-sync:
>
> ps -e -o "pid ppid args" | grep jpilot-sync
>
> will list both the PID and the PPID ("parent process ID") of jpilot-sync.
> Then you can 'ps -e | grep <PPID>', where <PPID> is the PPID determined in
> the first step.
>
> Cheers,
>
> Carlo
>
> Eamann O Ruairc wrote:
>
>> Hi Jason!
>>
>> I have tried to make sure that jpilot-sync was not running in duplicate
>> by killing one of the two procs. before syncing, but that did not make
>> any difference.
>>
>> When I launch the sync from the Zire I get four messages on the Zire in
>> fairly quick succession:
>>
>> - Connecting...
>> - Identifying the user...
>> - Cleaning up
>> - Hot sync finished...
>>
>> Obviously there is no mention of addresses, todo's, etc. and in fact
>> nothing is backed up.
>>
>> When I launch the sync from JP, generally I get:
>>
>> Syncing on device /dev/pilot
>> Press the HotSync button now
>>
>> Often I get in addition:
>> pi_bind error: /dev/pilot No such file or directory
>> Check your serial port and settings
>> Exiting with status SYNC_ERROR_BIND
>> Finished
>>
>> Sometimes I get
>> Press the HotSync button now or kill "xxx"
>>
>> Here's the print-out from several usages of ps ax | grep pilot:
>>
>> root at eamann-laptop:/home/eamann# ps ax | grep pilot
>> 14358 ? S 0:00 jpilot
>> 15226 ? S 0:00 jpilot
>> 15317 pts/0 R+ 0:00 grep pilot
>> root at eamann-laptop:/home/eamann# kill 15226
>> 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
>> 15413 pts/0 R+ 0:00 grep pilot
>> root at eamann-laptop:/home/eamann# kill 15360
>> root at eamann-laptop:/home/eamann# ps ax | grep pilot
>> 15837 ? S 0:00 jpilot
>> 15895 ? R 0:08 jpilot
>> 15912 pts/0 R+ 0:00 grep pilot
>> root at eamann-laptop:/home/eamann# kill 15895
>>
>> 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?
>>
>> Thank you once again for taking time to reply!
>>
>> Eamann
>>
>>
>> Jason Day wrote:
>>
>>> On Tue, Dec 05, 2006 at 02:42:18PM +0100, Eamann O Ruairc wrote:
>>>
>>>
>>>> When I did grep jpilot-sync /etc/udev/rules.d/*.rules, that produced
>>>> nothing in the terminal, but when I went into udev/rules.d, I found this:
>>>>
>>>> # Create /dev/pilot symlink for Palm Pilots
>>>> KERNEL=="ttyUSB*", SYSFS{product}=="Palm Handheld*|Handspring *", \
>>>> SYMLINK+="pilot"
>>>>
>>>>
>>> That's normal.
>>>
>>>
>>>
>>>> For the hotplug, apparently there is no such directory:
>>>> eamann at eamann-laptop:~$ grep -r jpilot-sync /etc/hotplug
>>>> grep: /etc/hotplug: No such file or directory
>>>>
>>>>
>>> That's also ok. I didn't know if your system used hotplug or not; it
>>> looks like it doesn't.
>>>
>>>
>>>
>>>> Any ideas?
>>>>
>>>>
>>> Is jpilot-sync still running? If so, kill it and try syncing again.
>>> Before you sync, make sure there are no other sync programs running:
>>> ps ax | grep pilot
>>>
>>> Jason
>>>
>>>
>> _______________________________________________
>> jpilot mailing list
>> jpilot at jpilot.org
>> http://www.jpilot.org/mailman/listinfo/jpilot
>>
>
>
>
More information about the jpilot mailing list