gnomepilot2 gpilotd

[Bob Van Valzah]

Joe, Thanks for your advice.

I've gotten over the gpilotd starting problems for now.  I also managed
to clean out the pilot state with rm -r -f ~/.gnome2/gnome-pilot.d

Now I'm back to the same old problem (though now it's a bit more easily
reproduced).  When the druid first starts to talk to gpilotd to receive
the user name and ID from the Palm, gpilotd exits:

gpilotd-Message: corba: get_pilots(...)
gpilotd-Message: corba: get_pilots(...)
gpilotd-Message: corba: get_pilots(...)
gpilotd-Message: Exiting (caught SIGTERM)...
Terminated

The first 3 lines are apparently the once per second checking to see if
the sync button has been pressed.  But the "caught SIGTERM" line pops
out and gpilotd exits as soon as the druid goes to read the user name
and ID.

I tried running gpilotd under truss to figure out what what was causing
the SIGTERM, but that didn't help.  (Gpilotd apparently forks or does
all its work in a child process or thread or something that keeps the
work it does from being trussed.)

So I'm still stumped.  All help or debugging advice appreciated.

	Thanks,
	
	Bob

On Tue, 2003-04-08 at 16:31, Joe Marcus Clarke wrote:
> On Tue, 2003-04-08 at 17:20, Bob Van Valzah wrote:
> > Is there any trick to making gnomepilot2 work?  I just did a
> > pkg_deinstall -f gnomepilot and then built gnomepilot2 from the
> > port.  I can't figure out who's supposed to start gpilotd.  Any hints there?
> 
> It's probably supposed to start when you login to GNOME (i.e. as part of
> gnome-session's startup).
> 
> >  
> > I did start it manually and got the druid to run, but then it exited
> > before it could sense the user name and ID from the Palm.  I kept
> > restarting gpilotd and pressed on with the druid and eventually got it
> > finished, but with the GCOS user name and UID instead of anything read
> > from the Palm.  I don't want to clobber what I have in there so I
> > deleted that Palm but am unable to add a new one.  Every time I hit
> > "Get from pilot" in the applet, it just times out.  I'm stuck.
> > 
> > Is there any way I can nuke the half-baked Pilot config I have now and
> > start over?  All advice appreciated.
> 
> I believe it's all stored in gconf.  You should be able to go throw
> ~/.gconf, and find the gpilot prefs, and remove them.
> 
> Joe
> 
> > 
> > 	Thanks,
> > 
> > 	Bob
> > _______________________________________________
> > freebsd-gnome at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
> > To unsubscribe, send any mail to "freebsd-gnome-unsubscribe at freebsd.org"