Er, looks like I scored an own-goal here. The command > eamann at eamann-laptop:~$ ps -e -o "pid ppid args" | grep jpilot-sync > 7234 7136 grep jpilot-sync ...did not pick up jpilot-sync, but rather the "grep jpilot-sync" part of the just-issued command-line. It looks to me as if you don't have jpilot-sync running at all, or at least you didn't when you were running this test. I assume you must have killed the jpilot-sync process. I don't really know whether its presence was related to your sync problem or not. If you think it might have been, you may wish to restore your system to the state it was in originally (when you detected jpilot-sync running), perhaps by means of a reboot, and then re-run the test. The mystery jpilot-sync process may turn out to be a red herring, but we can't know until it's run to ground. Cheers, Carlo -- Carlo Graziani (773) 702-7973 (Voice) Department of Astronomy and Astrophysics (773) 702-6645 (FAX) University of Chicago 5640 South Ellis Avenue | If the free market really allocates resources Chicago, IL 60637 | efficiently, why does LA have four times as carlo at oddjob.uchicago.edu | many plastic surgeons as brain surgeons?
More information about the jpilot mailing list