Your message dated Sun, 21 May 2006 00:14:36 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#329260: gpsd: report failure upon 2nd instance
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gpsd
Version: 2.28-2
Severity: wishlist
There should be some failure reported upon starting second instances.
# gpsd && gpsd && gpsd && echo $?
0
--- End Message ---
--- Begin Message ---
On Fri, 2005-09-16 at 10:43 +0800, Dan Jacobson wrote:
> Package: gpsd
> Version: 2.28-2
> Severity: wishlist
>
> There should be some failure reported upon starting second instances.
> # gpsd && gpsd && gpsd && echo $?
> 0
Hi,
in principal, there is nothing wrong with starting several instances of
gpsd. Think different instances of gpsd being attached to different gps
devices and listening on different network ports.
You only get into trouble if you try to bind to the same network port
more than once. If gpsd detaches from the terminal and runs as a daemon,
an error is reported to syslog:
May 20 23:55:45 mother gpsd[15105]: gpsd: Can't bind to port gpsd
May 20 23:55:45 mother gpsd[15105]: gpsd: command socket create failed,
netlib error -1
The exit code of 0 only signifies that gpsd was able to fork and detach.
When run with -N, gpsd doesn't detach, the error message is sent to the
terminal, and $? is 2:
(#538)[EMAIL PROTECTED]:~$ gpsd -N /dev/gps0 ; echo $?
gpsd: Can't bind to port gpsd
gpsd: command socket create failed, netlib error -1
2
There is a patch in upstream's SVN to make the error message even more
verbose: "gpsd: Maybe gpsd is already running!".
I hope this answers your concerns, and you don't mind me closing this
bug.
Cheers, Til
--- End Message ---
