How can I automatically launch GPSD on startup?
I am trying to figure out, what is preventing gpsd from automatically connecting to an external GPS BU 353 dongle via USB and receiving data. I have the same issue on both of my laptops (with different hardware), so this is purely a software configuration issue.
I have managed to get gpsd working manually, using the following steps, but every time my machine is powered off, I must go through these steps again.
sudo killall gpsd
Remove any sockets
gpsdmight have left behind with :
sudo rm /var/run/gpsd.sock
Check the device path:
dmesg - which shows PLU353
Ensure no other programs are using the device. There are none listed
lsof -n | grep /dev/ttyUSB0
Manually launch
gpsd:
sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock
xgpssees the GPS output - so this works
My best guesses are that gpsd needs to join a group or be given additional permissions, or alternatively, that it is an issue with udev configuration. But I am blundering about in the dark, just making wild guesses.
16.04 configuration
edited Feb 24 at 20:23
Tim
20k1486141
asked Feb 24 at 14:54
Geoffrey-cGeoffrey-c
212
add a comment |
I am trying to figure out, what is preventing gpsd from automatically connecting to an external GPS BU 353 dongle via USB and receiving data. I have the same issue on both of my laptops (with different hardware), so this is purely a software configuration issue.
I have managed to get gpsd working manually, using the following steps, but every time my machine is powered off, I must go through these steps again.
sudo killall gpsd
Remove any sockets
gpsdmight have left behind with :
sudo rm /var/run/gpsd.sock
Check the device path:
dmesg - which shows PLU353
Ensure no other programs are using the device. There are none listed
lsof -n | grep /dev/ttyUSB0
Manually launch
gpsd:
sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock
xgpssees the GPS output - so this works
My best guesses are that gpsd needs to join a group or be given additional permissions, or alternatively, that it is an issue with udev configuration. But I am blundering about in the dark, just making wild guesses.
16.04 configuration
edited Feb 24 at 20:23
Tim
20k1486141
asked Feb 24 at 14:54
Geoffrey-cGeoffrey-c
212
Rather thanlsof -n | grep /dev/ttyUSB0, I'd usesudo lsof /dev/ttyUSB0- no need togrep
– waltinator
Feb 24 at 15:18
1
Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?
– N0rbert
Feb 24 at 15:33
This has 2 answers from high-reputation (~20k) users, and it still hasn't been edited! Guys - tidy it up when you answer, it's a key part of keeping this site high-quality! @waltinator, remember to try to fix everything in the question when you edit it!
– Tim
Feb 24 at 20:19
add a comment |
I am trying to figure out, what is preventing gpsd from automatically connecting to an external GPS BU 353 dongle via USB and receiving data. I have the same issue on both of my laptops (with different hardware), so this is purely a software configuration issue.
I have managed to get gpsd working manually, using the following steps, but every time my machine is powered off, I must go through these steps again.
sudo killall gpsd
Remove any sockets
gpsdmight have left behind with :
sudo rm /var/run/gpsd.sock
Check the device path:
dmesg - which shows PLU353
Ensure no other programs are using the device. There are none listed
lsof -n | grep /dev/ttyUSB0
Manually launch
gpsd:
sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock
xgpssees the GPS output - so this works
My best guesses are that gpsd needs to join a group or be given additional permissions, or alternatively, that it is an issue with udev configuration. But I am blundering about in the dark, just making wild guesses.
16.04 configuration
edited Feb 24 at 20:23
Tim
20k1486141
asked Feb 24 at 14:54
Geoffrey-cGeoffrey-c
212
I am trying to figure out, what is preventing gpsd from automatically connecting to an external GPS BU 353 dongle via USB and receiving data. I have the same issue on both of my laptops (with different hardware), so this is purely a software configuration issue.
I have managed to get gpsd working manually, using the following steps, but every time my machine is powered off, I must go through these steps again.
sudo killall gpsd
Remove any sockets
gpsdmight have left behind with :
sudo rm /var/run/gpsd.sock
Check the device path:
dmesg - which shows PLU353
Ensure no other programs are using the device. There are none listed
lsof -n | grep /dev/ttyUSB0
Manually launch
gpsd:
sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock
xgpssees the GPS output - so this works
My best guesses are that gpsd needs to join a group or be given additional permissions, or alternatively, that it is an issue with udev configuration. But I am blundering about in the dark, just making wild guesses.
16.04 configuration
16.04 configuration
edited Feb 24 at 20:23
Tim
20k1486141
asked Feb 24 at 14:54
Geoffrey-cGeoffrey-c
212
edited Feb 24 at 20:23
Tim
20k1486141
asked Feb 24 at 14:54
Geoffrey-cGeoffrey-c
212
edited Feb 24 at 20:23
Tim
20k1486141
edited Feb 24 at 20:23
Tim
20k1486141
edited Feb 24 at 20:23
Tim
20k1486141
20k1486141
asked Feb 24 at 14:54
Geoffrey-cGeoffrey-c
212
asked Feb 24 at 14:54
Geoffrey-cGeoffrey-c
212
asked Feb 24 at 14:54
Geoffrey-cGeoffrey-c
212
212
Rather thanlsof -n | grep /dev/ttyUSB0, I'd usesudo lsof /dev/ttyUSB0- no need togrep
– waltinator
Feb 24 at 15:18
1
Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?
– N0rbert
Feb 24 at 15:33
This has 2 answers from high-reputation (~20k) users, and it still hasn't been edited! Guys - tidy it up when you answer, it's a key part of keeping this site high-quality! @waltinator, remember to try to fix everything in the question when you edit it!
– Tim
Feb 24 at 20:19
add a comment |
Rather thanlsof -n | grep /dev/ttyUSB0, I'd usesudo lsof /dev/ttyUSB0- no need togrep
– waltinator
Feb 24 at 15:18
1
Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?
– N0rbert
Feb 24 at 15:33
This has 2 answers from high-reputation (~20k) users, and it still hasn't been edited! Guys - tidy it up when you answer, it's a key part of keeping this site high-quality! @waltinator, remember to try to fix everything in the question when you edit it!
– Tim
Feb 24 at 20:19
Rather than
lsof -n | grep /dev/ttyUSB0, I'd use sudo lsof /dev/ttyUSB0 - no need to grep– waltinator
Feb 24 at 15:18
Rather than
lsof -n | grep /dev/ttyUSB0, I'd use sudo lsof /dev/ttyUSB0 - no need to grep– waltinator
Feb 24 at 15:18
1
1
Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?
– N0rbert
Feb 24 at 15:33
Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?
– N0rbert
Feb 24 at 15:33
This has 2 answers from high-reputation (~20k) users, and it still hasn't been edited! Guys - tidy it up when you answer, it's a key part of keeping this site high-quality! @waltinator, remember to try to fix everything in the question when you edit it!
– Tim
Feb 24 at 20:19
This has 2 answers from high-reputation (~20k) users, and it still hasn't been edited! Guys - tidy it up when you answer, it's a key part of keeping this site high-quality! @waltinator, remember to try to fix everything in the question when you edit it!
– Tim
Feb 24 at 20:19
add a comment |
2 Answers
2
active
oldest
votes
You're correct - it is a group membership problem. First, see who owns the device:
ls -l /dev/ttyUSB0
On MY system, I don't have /dev/ttyUSB0, so I'll use /dev/ttyS0 instead
walt@bat:~(0)$ ls -l /dev/ttyS0
crw-rw---- 1 root dialout 4, 64 Feb 23 08:19 /dev/ttyS0
walt@bat:~(0)$
The output of the ls command shows that it's owned by root:dialout, and allows group access to the device.
Add your user to the dialout (or whatever is right for your system) group with:
sudo adduser $USER dialout
Then to make this group membership take effect, logout/login, OR newgrp dialout to start a shell with that group membership.
Check your group membership with /usr/bin/id.
answered Feb 24 at 15:05
waltinatorwaltinator
22.6k74169
Hi Waltinator, I have run and get the same output ls -l /dev/ttyUSB0 giviing crw-rw---- 1 root dialout 188, 0 Feb 24 19:10 /dev/ttyUSB0
– Geoffrey-c
Feb 24 at 18:17
Additionally, I am in the dialout group as I just posted and I also tried adding gpsd into the dialout group as well and rebooting, but no joy
– Geoffrey-c
Feb 24 at 18:33
add a comment |
- open TCP port 2947 in your firewall (if you wish other network clients access)
- in
terminal...
sudo adduser $USER dialout# add user to group dialout
sudo -H gedit /etc/default/gpsd# edit the gpsd settings file- change
DEVICES=""toDEVICES="/dev/ttyUSB0"# your /dev name may be different - save file and quit gedit
sudo systemctl restart gpsd# restart gpsd
gpsmon, cgps, and xgps will now work properly.
answered Feb 24 at 15:34
heynnemaheynnema
19.9k22158
Wrong device name, and from what can be seen in first post, he doesn't have to open any ports for it to work; only re-start gpsd as root.
– vidarlo
Feb 24 at 15:54
@vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.
– heynnema
Feb 24 at 16:13
@vidarlo please consider reversing your down vote. Thanks!
– heynnema
Feb 24 at 16:17
No, not unless you have modified/etc/ufw/before.rules, which by default allows all onlointerface. In addition, it should be noted that gpsd may use a socket as well, which does not touch the network stack at all. As I stated; in the question it works after restarting gpsd, without any modification to the firewall rules.
– vidarlo
Feb 24 at 16:45
@vidarlo ok... educate me... where is there any documentation about modifying/etc/ufw/before.rules, and what would you modify there? Also, re: tcp port... "Client applications will communicate with gpsd via a TCP/IP port, 2947 by default)".
– heynnema
Feb 24 at 16:55
|
show 15 more comments
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1120881%2fhow-can-i-automatically-launch-gpsd-on-startup%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You're correct - it is a group membership problem. First, see who owns the device:
ls -l /dev/ttyUSB0
On MY system, I don't have /dev/ttyUSB0, so I'll use /dev/ttyS0 instead
walt@bat:~(0)$ ls -l /dev/ttyS0
crw-rw---- 1 root dialout 4, 64 Feb 23 08:19 /dev/ttyS0
walt@bat:~(0)$
The output of the ls command shows that it's owned by root:dialout, and allows group access to the device.
Add your user to the dialout (or whatever is right for your system) group with:
sudo adduser $USER dialout
Then to make this group membership take effect, logout/login, OR newgrp dialout to start a shell with that group membership.
Check your group membership with /usr/bin/id.
answered Feb 24 at 15:05
waltinatorwaltinator
22.6k74169
Hi Waltinator, I have run and get the same output ls -l /dev/ttyUSB0 giviing crw-rw---- 1 root dialout 188, 0 Feb 24 19:10 /dev/ttyUSB0
– Geoffrey-c
Feb 24 at 18:17
Additionally, I am in the dialout group as I just posted and I also tried adding gpsd into the dialout group as well and rebooting, but no joy
– Geoffrey-c
Feb 24 at 18:33
add a comment |
You're correct - it is a group membership problem. First, see who owns the device:
ls -l /dev/ttyUSB0
On MY system, I don't have /dev/ttyUSB0, so I'll use /dev/ttyS0 instead
walt@bat:~(0)$ ls -l /dev/ttyS0
crw-rw---- 1 root dialout 4, 64 Feb 23 08:19 /dev/ttyS0
walt@bat:~(0)$
The output of the ls command shows that it's owned by root:dialout, and allows group access to the device.
Add your user to the dialout (or whatever is right for your system) group with:
sudo adduser $USER dialout
Then to make this group membership take effect, logout/login, OR newgrp dialout to start a shell with that group membership.
Check your group membership with /usr/bin/id.
answered Feb 24 at 15:05
waltinatorwaltinator
22.6k74169
Hi Waltinator, I have run and get the same output ls -l /dev/ttyUSB0 giviing crw-rw---- 1 root dialout 188, 0 Feb 24 19:10 /dev/ttyUSB0
– Geoffrey-c
Feb 24 at 18:17
Additionally, I am in the dialout group as I just posted and I also tried adding gpsd into the dialout group as well and rebooting, but no joy
– Geoffrey-c
Feb 24 at 18:33
add a comment |
You're correct - it is a group membership problem. First, see who owns the device:
ls -l /dev/ttyUSB0
On MY system, I don't have /dev/ttyUSB0, so I'll use /dev/ttyS0 instead
walt@bat:~(0)$ ls -l /dev/ttyS0
crw-rw---- 1 root dialout 4, 64 Feb 23 08:19 /dev/ttyS0
walt@bat:~(0)$
The output of the ls command shows that it's owned by root:dialout, and allows group access to the device.
Add your user to the dialout (or whatever is right for your system) group with:
sudo adduser $USER dialout
Then to make this group membership take effect, logout/login, OR newgrp dialout to start a shell with that group membership.
Check your group membership with /usr/bin/id.
answered Feb 24 at 15:05
waltinatorwaltinator
22.6k74169
You're correct - it is a group membership problem. First, see who owns the device:
ls -l /dev/ttyUSB0
On MY system, I don't have /dev/ttyUSB0, so I'll use /dev/ttyS0 instead
walt@bat:~(0)$ ls -l /dev/ttyS0
crw-rw---- 1 root dialout 4, 64 Feb 23 08:19 /dev/ttyS0
walt@bat:~(0)$
The output of the ls command shows that it's owned by root:dialout, and allows group access to the device.
Add your user to the dialout (or whatever is right for your system) group with:
sudo adduser $USER dialout
Then to make this group membership take effect, logout/login, OR newgrp dialout to start a shell with that group membership.
Check your group membership with /usr/bin/id.
answered Feb 24 at 15:05
waltinatorwaltinator
22.6k74169
answered Feb 24 at 15:05
waltinatorwaltinator
22.6k74169
answered Feb 24 at 15:05
waltinatorwaltinator
22.6k74169
answered Feb 24 at 15:05
waltinatorwaltinator
22.6k74169
22.6k74169
Hi Waltinator, I have run and get the same output ls -l /dev/ttyUSB0 giviing crw-rw---- 1 root dialout 188, 0 Feb 24 19:10 /dev/ttyUSB0
– Geoffrey-c
Feb 24 at 18:17
Additionally, I am in the dialout group as I just posted and I also tried adding gpsd into the dialout group as well and rebooting, but no joy
– Geoffrey-c
Feb 24 at 18:33
add a comment |
Hi Waltinator, I have run and get the same output ls -l /dev/ttyUSB0 giviing crw-rw---- 1 root dialout 188, 0 Feb 24 19:10 /dev/ttyUSB0
– Geoffrey-c
Feb 24 at 18:17
Additionally, I am in the dialout group as I just posted and I also tried adding gpsd into the dialout group as well and rebooting, but no joy
– Geoffrey-c
Feb 24 at 18:33
Hi Waltinator, I have run and get the same output ls -l /dev/ttyUSB0 giviing crw-rw---- 1 root dialout 188, 0 Feb 24 19:10 /dev/ttyUSB0
– Geoffrey-c
Feb 24 at 18:17
Hi Waltinator, I have run and get the same output ls -l /dev/ttyUSB0 giviing crw-rw---- 1 root dialout 188, 0 Feb 24 19:10 /dev/ttyUSB0
– Geoffrey-c
Feb 24 at 18:17
Additionally, I am in the dialout group as I just posted and I also tried adding gpsd into the dialout group as well and rebooting, but no joy
– Geoffrey-c
Feb 24 at 18:33
Additionally, I am in the dialout group as I just posted and I also tried adding gpsd into the dialout group as well and rebooting, but no joy
– Geoffrey-c
Feb 24 at 18:33
add a comment |
- open TCP port 2947 in your firewall (if you wish other network clients access)
- in
terminal...
sudo adduser $USER dialout# add user to group dialout
sudo -H gedit /etc/default/gpsd# edit the gpsd settings file- change
DEVICES=""toDEVICES="/dev/ttyUSB0"# your /dev name may be different - save file and quit gedit
sudo systemctl restart gpsd# restart gpsd
gpsmon, cgps, and xgps will now work properly.
answered Feb 24 at 15:34
heynnemaheynnema
19.9k22158
Wrong device name, and from what can be seen in first post, he doesn't have to open any ports for it to work; only re-start gpsd as root.
– vidarlo
Feb 24 at 15:54
@vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.
– heynnema
Feb 24 at 16:13
@vidarlo please consider reversing your down vote. Thanks!
– heynnema
Feb 24 at 16:17
No, not unless you have modified/etc/ufw/before.rules, which by default allows all onlointerface. In addition, it should be noted that gpsd may use a socket as well, which does not touch the network stack at all. As I stated; in the question it works after restarting gpsd, without any modification to the firewall rules.
– vidarlo
Feb 24 at 16:45
@vidarlo ok... educate me... where is there any documentation about modifying/etc/ufw/before.rules, and what would you modify there? Also, re: tcp port... "Client applications will communicate with gpsd via a TCP/IP port, 2947 by default)".
– heynnema
Feb 24 at 16:55
|
show 15 more comments
- open TCP port 2947 in your firewall (if you wish other network clients access)
- in
terminal...
sudo adduser $USER dialout# add user to group dialout
sudo -H gedit /etc/default/gpsd# edit the gpsd settings file- change
DEVICES=""toDEVICES="/dev/ttyUSB0"# your /dev name may be different - save file and quit gedit
sudo systemctl restart gpsd# restart gpsd
gpsmon, cgps, and xgps will now work properly.
answered Feb 24 at 15:34
heynnemaheynnema
19.9k22158
Wrong device name, and from what can be seen in first post, he doesn't have to open any ports for it to work; only re-start gpsd as root.
– vidarlo
Feb 24 at 15:54
@vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.
– heynnema
Feb 24 at 16:13
@vidarlo please consider reversing your down vote. Thanks!
– heynnema
Feb 24 at 16:17
No, not unless you have modified/etc/ufw/before.rules, which by default allows all onlointerface. In addition, it should be noted that gpsd may use a socket as well, which does not touch the network stack at all. As I stated; in the question it works after restarting gpsd, without any modification to the firewall rules.
– vidarlo
Feb 24 at 16:45
@vidarlo ok... educate me... where is there any documentation about modifying/etc/ufw/before.rules, and what would you modify there? Also, re: tcp port... "Client applications will communicate with gpsd via a TCP/IP port, 2947 by default)".
– heynnema
Feb 24 at 16:55
|
show 15 more comments
- open TCP port 2947 in your firewall (if you wish other network clients access)
- in
terminal...
sudo adduser $USER dialout# add user to group dialout
sudo -H gedit /etc/default/gpsd# edit the gpsd settings file- change
DEVICES=""toDEVICES="/dev/ttyUSB0"# your /dev name may be different - save file and quit gedit
sudo systemctl restart gpsd# restart gpsd
gpsmon, cgps, and xgps will now work properly.
answered Feb 24 at 15:34
heynnemaheynnema
19.9k22158
- open TCP port 2947 in your firewall (if you wish other network clients access)
- in
terminal...
sudo adduser $USER dialout# add user to group dialout
sudo -H gedit /etc/default/gpsd# edit the gpsd settings file- change
DEVICES=""toDEVICES="/dev/ttyUSB0"# your /dev name may be different - save file and quit gedit
sudo systemctl restart gpsd# restart gpsd
gpsmon, cgps, and xgps will now work properly.
answered Feb 24 at 15:34
heynnemaheynnema
19.9k22158
edited Feb 25 at 14:22
answered Feb 24 at 15:34
heynnemaheynnema
19.9k22158
answered Feb 24 at 15:34
heynnemaheynnema
19.9k22158
answered Feb 24 at 15:34
heynnemaheynnema
19.9k22158
19.9k22158
Wrong device name, and from what can be seen in first post, he doesn't have to open any ports for it to work; only re-start gpsd as root.
– vidarlo
Feb 24 at 15:54
@vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.
– heynnema
Feb 24 at 16:13
@vidarlo please consider reversing your down vote. Thanks!
– heynnema
Feb 24 at 16:17
No, not unless you have modified/etc/ufw/before.rules, which by default allows all onlointerface. In addition, it should be noted that gpsd may use a socket as well, which does not touch the network stack at all. As I stated; in the question it works after restarting gpsd, without any modification to the firewall rules.
– vidarlo
Feb 24 at 16:45
@vidarlo ok... educate me... where is there any documentation about modifying/etc/ufw/before.rules, and what would you modify there? Also, re: tcp port... "Client applications will communicate with gpsd via a TCP/IP port, 2947 by default)".
– heynnema
Feb 24 at 16:55
|
show 15 more comments
Wrong device name, and from what can be seen in first post, he doesn't have to open any ports for it to work; only re-start gpsd as root.
– vidarlo
Feb 24 at 15:54
@vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.
– heynnema
Feb 24 at 16:13
@vidarlo please consider reversing your down vote. Thanks!
– heynnema
Feb 24 at 16:17
No, not unless you have modified/etc/ufw/before.rules, which by default allows all onlointerface. In addition, it should be noted that gpsd may use a socket as well, which does not touch the network stack at all. As I stated; in the question it works after restarting gpsd, without any modification to the firewall rules.
– vidarlo
Feb 24 at 16:45
@vidarlo ok... educate me... where is there any documentation about modifying/etc/ufw/before.rules, and what would you modify there? Also, re: tcp port... "Client applications will communicate with gpsd via a TCP/IP port, 2947 by default)".
– heynnema
Feb 24 at 16:55
Wrong device name, and from what can be seen in first post, he doesn't have to open any ports for it to work; only re-start gpsd as root.
– vidarlo
Feb 24 at 15:54
Wrong device name, and from what can be seen in first post, he doesn't have to open any ports for it to work; only re-start gpsd as root.
– vidarlo
Feb 24 at 15:54
@vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.
– heynnema
Feb 24 at 16:13
@vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.
– heynnema
Feb 24 at 16:13
@vidarlo please consider reversing your down vote. Thanks!
– heynnema
Feb 24 at 16:17
@vidarlo please consider reversing your down vote. Thanks!
– heynnema
Feb 24 at 16:17
No, not unless you have modified
/etc/ufw/before.rules, which by default allows all on lo interface. In addition, it should be noted that gpsd may use a socket as well, which does not touch the network stack at all. As I stated; in the question it works after restarting gpsd, without any modification to the firewall rules.– vidarlo
Feb 24 at 16:45
No, not unless you have modified
/etc/ufw/before.rules, which by default allows all on lo interface. In addition, it should be noted that gpsd may use a socket as well, which does not touch the network stack at all. As I stated; in the question it works after restarting gpsd, without any modification to the firewall rules.– vidarlo
Feb 24 at 16:45
@vidarlo ok... educate me... where is there any documentation about modifying
/etc/ufw/before.rules, and what would you modify there? Also, re: tcp port... "Client applications will communicate with gpsd via a TCP/IP port, 2947 by default)".– heynnema
Feb 24 at 16:55
@vidarlo ok... educate me... where is there any documentation about modifying
/etc/ufw/before.rules, and what would you modify there? Also, re: tcp port... "Client applications will communicate with gpsd via a TCP/IP port, 2947 by default)".– heynnema
Feb 24 at 16:55
|
show 15 more comments
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1120881%2fhow-can-i-automatically-launch-gpsd-on-startup%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Rather than
lsof -n | grep /dev/ttyUSB0, I'd usesudo lsof /dev/ttyUSB0- no need togrep– waltinator
Feb 24 at 15:18
1
Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?
– N0rbert
Feb 24 at 15:33
This has 2 answers from high-reputation (~20k) users, and it still hasn't been edited! Guys - tidy it up when you answer, it's a key part of keeping this site high-quality! @waltinator, remember to try to fix everything in the question when you edit it!
– Tim
Feb 24 at 20:19