On 9/26/06, Russ Button <russ at button.com> wrote: > Roshan Mansinghani wrote: > > 2. Using hal/ivman to launch the jpilot sync in the event that the > > hotsync button is pressed. > > This is great because I have also have a Treo 600. > > > > > This requires you to have hal and ivman installed. Make sure that hal > > is running (the daemon's executable is named hald). The first thing > > we need to do is find out what hal events are generated once the > > hotsync button is pressed. In order to do this, open a terminal and > > launch the following command: lshal --monitor. > > Looking on my box it appears that hald is already there. Good. > > Then, watch the output once you hit the hotsync button. I use a Treo > > 600, and there were three events generated when I pressed the hotsync > > button. The event I used was the last event, which looks something > > like: > > > > /org/freedesktop/Hal/devices/usb_device_82d_300_PalmSN12345678_usbraw > > I saw the exact same thing. Good. > > > > You may have to do some experimenation to find the best hal event to > > trigger off of. Once you figure out which hal event to use, it is > > time to use ivman to launch the jpilot sync program. So, first edit: > > > > /etc/ivman/IvmConfigActions.xml > > > > And insert the following lines: > > > > <ivm:Match name="hal.info.udi" > > value="/org/freedesktop/Hal/devices/usb_device_82d_300_PalmSN12345678_usbraw"> > > > > <ivm:Option name="exec" value="jpilot -s" /> > > </ivm:Match> > > But after all of this, I'm not getting the hotsyncing with the one button. > > This is where I have some issues. I didn't have ivman installed, so I > pulled it down and it seems to have installed OK. Neither you nor the > ivman page says much about how it needs to be started up and managed. > From the ivman man page: > > "For automount purposes, Ivman should be run once from a > system-wide > init script and once per user session (e.g., create a > link to > /usr/bin/ivman in ~/.kde/Autostart or put an entry for > /usr/bin/ivman > in gnome-session-manager). " > > I first fired up ivman as root, and then invoked it as myself manually. So, you have to make sure ivman is running (I know it works as the user, I don't know about root). I assume that is what you meant. > > One thing I don't understand why the value in the ivman config file > mentions the path > > /org/freedesktop/Hal/devices > > when it doesn't exist, or get installed as part of the ivman install. > What's being referenced doesn't exist so far as I can tell, nor is there > any "Hal" directory created anywhere as part of the ivman install. That is not a path on your file system but a classification system through hal and the freedesktop specification. It is a way to categorize devices, as far as I know. You do have jpilot installed, right? Sorry for the dumb questions, I am just trying to debug. Also, try running it with the jpilot program running and the jpilot program not running. > _______________________________________________ > jpilot mailing list > jpilot at jpilot.org > http://www.jpilot.org/mailman/listinfo/jpilot >
More information about the jpilot mailing list