Hi Jason,
Thank you for trying to help too!
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"
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
Any ideas?
Eamann
Jason Day wrote:
> On Sun, Dec 03, 2006 at 08:53:17PM +0100, Eamann O Ruairc wrote:
>
>> /root at eamann-laptop:/home/eamann# ps ax | grep jpilot
>> 5266 ? S 0:03 jpilot
>> 5563 ? S 0:00 /bin/sh -c /usr/bin/jpilot-sync
>> 5564 ? R 2:52 /usr/bin/jpilot-sync
>> 5569 ? S 0:00 /bin/sh -c /usr/bin/jpilot-sync
>> 5570 ? R 2:52 /usr/bin/jpilot-sync/
>>
>
> This isn't right: something is starting jpilot-sync, which is a program
> in the jpilot distribution that syncs without using the jpilot GUI. If
> you try to sync with both jpilot-sync and the jpilot GUI they will
> interfere with each other and cause problems.
>
> Check your udev rules and possibly hotplug scripts to see if anything is
> invoking jpilot-sync automatically. Udev rules are in the
> /etc/udev/rules.d/ directory; try running this command:
>
> grep jpilot-sync /etc/udev/rules.d/*.rules
>
> If that matches anything, post the results back here. If not, try
> searching for a hotplug script:
>
> grep -r jpilot-sync /etc/hotplug
>
>
> HTH,
> Jason
>
More information about the jpilot mailing list