stoping gpilotd cold

[Carlos Morgado <chbm chbm nu>]

Somehow i managed to keep gpilotd from doing anything by messing up the
gnome-pilot.d. I tried cvs and .48 gpilotds and all said '/dev/pilot has 0
events' and stoped the sync.
then i started gpilotd-capplet, moved gnome-pilot.d out of the way and made
it regenerate the config. all worked fine.

i can't see any fundamental diference between the old config (gnome-pilot.d
tgz attached) and the new one.
this situation shouldn't arrise in the wild anyway cause i got to this
state by messing with conduits,cvs and versions :)

cheers


-- 
Carlos Morgado - chbm(at)chbm(dot)nu - http://chbm.nu/ -- gpgkey: 0x1FC57F0A 
http://wwwkeys.pgp.net/ FP:0A27 35D3 C448 3641 0573 6876 2A37 4BB2 1FC5 7F0A
Q: Why do computers have a reset button ?
A: Windows

gnome-pilot-d-b0rken.tgz