Once I boot, synchronizing my Visor using Kpilot is very straightforward. No problem.

Then I keep working and a few hours later I try syncing again, but it fails. I get a message on my Visor: "No connection could be established".

Facing this problem, I used to reboot to be able to synchronize again.

After some time I found that doing:

pstree -p
Kill [kpilotDaemon PID]
kpilotDaemon


would help me synchronize again, without need to reboot.

However, sometimes not even that procedure helps, and I have to reboot anyway.


Could somebody explain why this would happen, and what would be a better way to efficiently synchronize every single time without this juggling?


Your ideas will be highly appreciated.

Not sure, but for me, dmesg in konsole tells me both /dev/ttyUSB0 and /dev/ttyUSB1 the first time I press it. The second time, it tells me the Palm is connected to /dev/ttyUSB2 and /dev/ttyUSB3.

Hotplugging is the problem, and unfortunately, there is no good solution, other than perhaps to create a script that kills the old daemon and restarts it.

Linux does not necessarily know where to find the palm pilot. If you point the kpilot deamon to the USB ports, it will look for it and find it where it says it is, that time. Remember USB is pretty dynamic. You can add and remove devices all day long. Unfortunately hotplugging interferes because the port address might be reassigned. Restarting the deamon is the only current solution to this.

Hotplugging in Linux is not as developed as it is in Windoze. It's pretty much an add-on technology, and devices tend to be very proprietary. That makes it difficult to get USB working well, especially with few hardware manufacturers going out of their way to help develop for Linux.

I find that if I try to synch twice with kpilot it won't work. However, if I close the program and restart it, than I am ok (I have kpilot set to close the deamon upon exit). As I said before, you can write a script that will kill and restart the process and assign it to a icon on your desktop. You can call it Pilot Refresh or something. Alternatively, set kiplot to kill the deamon on exit and close kpilot after synching like I do.

Thank you, JaseP.
I wrote this simple script:

#! /bin/bash
sudo killproc /opt/kde3/bin/kpilotDaemon
kpilotDaemon

Previously, I used visudo to run sudo without a password and it works.
However, when I run the script as a regular user, I get this message:

sudo: killproc: command not found

Doesn't sudo let me run just any command, as if I were root? This is my sudoers file:

# sudoers file.
#
# This file MUST be edited with the 'visudo' command as root.
#
# See the sudoers man page for the details on how to write a sudoers file.
#
# Host alias specification
# User alias specification
# Cmnd alias specificationxgandalf ALL=(ALL) NOPASSWD: ALL


# Defaults specification
Defaults targetpw
%users ALL=(ALL) ALL
# User privilege specification
root ALL=(ALL) ALL
# Uncomment to allow people in group wheel to run all commands
# %wheel ALL=(ALL) ALL
# Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL
# Samples
# %users ALL=/sbin/mount /cdrom,/sbin/umount /cdrom
# %users localhost=/sbin/shutdown -h now
myusername ALL=(ALL) NOPASSWD: ALL