> I wish I could wait for the new release of gpsd, but I have to do a delivery
> of my project, so they wont be much of a help for now ...
> but This sounds good!
> > I guess as a hacky workaround, you could always do somehing like
> > launch cgps in the background, sleep for a few seconds, kill it and
> > launch cgps again.
> how can I do this?
> in my /root/.profile I just have:
> gpsd /dev/ttyS2
> ./cgps | tee /dev/ttyS2
> How can I start cgps in the background after some sleep and delays and
> terminate it so that I can restart cgps for the second time?
You can do something like this
( ./cgps | tee /dev/ttyS2 ) &
You may find that just doing:
./cgps | tee/dev/ttyS2
is all that's required. This gives gpsd a chance to get initialized
before starting cgps.
> Also, I have noticed ... with the .profile that I have now, if cgps is
> running and I want to reboot (using the button on the board) the gumstix
> hangs up and I have to reset with power connection. How can I make cgps to
> finish and gumstix reboot with the reset button on the gumstix board!
Are you talking about the reset button on the gumstix board? If so, it
will reset the processor regardless of what's running. Or are you
talking about some other button?
What do you mean by the "gumstix hangs up"? Hangs up where? What was
output to the console?
Vancouver, BC, Canada