How can I automatically launch GPSD on startup?How do I allow non-root access to /ttyUSB0 on 12.04?How can I...

Would water spill from a bowl in a Bag of Holding?

Crack the bank account's password!

Does copper wire need to say it's copper?

Other than edits for international editions, did Harry Potter and the Philosopher's Stone receive errata?

Is layered encryption more secure than long passwords?

How bad is a Computer Science course that doesn't teach Design Patterns?

Plausible reason for gold-digging ant

Fraction within another fraction

Is it possible to detect 100% of SQLi with a simple regex?

Does rolling friction increase speed of a wheel?

smartctl reports overall health test as passed but the tests failed?

Can you say "leftside right"?

How can I prevent an oracle who can see into the past from knowing everything that has happened?

How to check if remote-signer is working as expected?

What can I do to encourage my players to use their consumables?

Minimum Viable Product for RTS game?

How do I fight with Heavy Armor as a Wizard with Tenser's Transformation?

Is there any good browser plugin or tool to quickly identify any security issues of a web site?

What would be some possible ways of escaping higher gravity planets?

What species should be used for storage of human minds?

If angels and devils are the same species, why would their mortal offspring appear physically different?

Homeostasis logic/math problem

Is there a way to pause a running process on Linux systems and resume later?

Modern Algebraic Geometry and Analytic Number Theory



How can I automatically launch GPSD on startup?


How do I allow non-root access to /ttyUSB0 on 12.04?How can I delay a specific program on startup?How can I stop workspaces from switching automatically to other workspaces when selecting different applications?How can I launch Ubuntu Variants and Betas on GCE?How can I check for updates automatically but not on startup?Discord Won't Launch 16.04How to startup a script automatically after loginhow can I recover /etc/security/limits.conf?SSH Private Key doesn't automatically load on startupHow can I launch any application using terminal?How to run a shell script automatically after startup and wake-up from hibernate?













4















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.




  1. sudo killall gpsd



  2. Remove any sockets gpsd might have left behind with :



    sudo rm /var/run/gpsd.sock




  3. Check the device path:



    dmesg - which shows PLU353 



  4. Ensure no other programs are using the device. There are none listed



    lsof -n | grep /dev/ttyUSB0



  5. Manually launch gpsd:



    sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock


  6. xgps sees 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.










share|improve this question









New contributor




Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Rather than lsof -n | grep /dev/ttyUSB0, I'd use sudo lsof /dev/ttyUSB0 - no need to grep

    – waltinator
    5 hours ago











  • Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?

    – N0rbert
    5 hours ago











  • 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
    41 mins ago


















4















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.




  1. sudo killall gpsd



  2. Remove any sockets gpsd might have left behind with :



    sudo rm /var/run/gpsd.sock




  3. Check the device path:



    dmesg - which shows PLU353 



  4. Ensure no other programs are using the device. There are none listed



    lsof -n | grep /dev/ttyUSB0



  5. Manually launch gpsd:



    sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock


  6. xgps sees 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.










share|improve this question









New contributor




Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Rather than lsof -n | grep /dev/ttyUSB0, I'd use sudo lsof /dev/ttyUSB0 - no need to grep

    – waltinator
    5 hours ago











  • Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?

    – N0rbert
    5 hours ago











  • 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
    41 mins ago
















4












4








4








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.




  1. sudo killall gpsd



  2. Remove any sockets gpsd might have left behind with :



    sudo rm /var/run/gpsd.sock




  3. Check the device path:



    dmesg - which shows PLU353 



  4. Ensure no other programs are using the device. There are none listed



    lsof -n | grep /dev/ttyUSB0



  5. Manually launch gpsd:



    sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock


  6. xgps sees 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.










share|improve this question









New contributor




Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












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.




  1. sudo killall gpsd



  2. Remove any sockets gpsd might have left behind with :



    sudo rm /var/run/gpsd.sock




  3. Check the device path:



    dmesg - which shows PLU353 



  4. Ensure no other programs are using the device. There are none listed



    lsof -n | grep /dev/ttyUSB0



  5. Manually launch gpsd:



    sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock


  6. xgps sees 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






share|improve this question









New contributor




Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 37 mins ago









Tim

19.9k1486141




19.9k1486141






New contributor




Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 6 hours ago









Geoffrey-cGeoffrey-c

211




211




New contributor




Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • Rather than lsof -n | grep /dev/ttyUSB0, I'd use sudo lsof /dev/ttyUSB0 - no need to grep

    – waltinator
    5 hours ago











  • Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?

    – N0rbert
    5 hours ago











  • 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
    41 mins ago





















  • Rather than lsof -n | grep /dev/ttyUSB0, I'd use sudo lsof /dev/ttyUSB0 - no need to grep

    – waltinator
    5 hours ago











  • Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?

    – N0rbert
    5 hours ago











  • 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
    41 mins ago



















Rather than lsof -n | grep /dev/ttyUSB0, I'd use sudo lsof /dev/ttyUSB0 - no need to grep

– waltinator
5 hours ago





Rather than lsof -n | grep /dev/ttyUSB0, I'd use sudo lsof /dev/ttyUSB0 - no need to grep

– waltinator
5 hours ago













Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?

– N0rbert
5 hours ago





Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?

– N0rbert
5 hours ago













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
41 mins ago







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
41 mins ago












2 Answers
2






active

oldest

votes


















7














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.






share|improve this answer
























  • 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
    2 hours ago











  • 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
    2 hours ago



















2















  • open TCP port 2947 in your firewall (if you wish other network clients access)

  • make sure your username is in group dialout

  • in terminal, edit /etc/default/gpsd



    • sudo -H gedit /etc/default/gpsd # edit the gpsd settings file

    • change DEVICES="" to DEVICES="/dev/ttyUSB0" # /dev name may be different

    • save and quit gedit


    • sudo systemctl restart gpsd # restart gpsd




gpsmon, cgps, and xgps will now work properly.






share|improve this answer


























  • 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
    5 hours ago











  • @vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.

    – heynnema
    4 hours ago











  • @vidarlo please consider reversing your down vote. Thanks!

    – heynnema
    4 hours ago











  • 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
    4 hours ago













  • @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
    4 hours ago











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
});


}
});






Geoffrey-c is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















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









7














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.






share|improve this answer
























  • 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
    2 hours ago











  • 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
    2 hours ago
















7














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.






share|improve this answer
























  • 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
    2 hours ago











  • 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
    2 hours ago














7












7








7







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.






share|improve this answer













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.







share|improve this answer












share|improve this answer



share|improve this answer










answered 5 hours ago









waltinatorwaltinator

22.5k74169




22.5k74169













  • 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
    2 hours ago











  • 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
    2 hours ago



















  • 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
    2 hours ago











  • 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
    2 hours ago

















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
2 hours ago





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
2 hours ago













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
2 hours ago





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
2 hours ago













2















  • open TCP port 2947 in your firewall (if you wish other network clients access)

  • make sure your username is in group dialout

  • in terminal, edit /etc/default/gpsd



    • sudo -H gedit /etc/default/gpsd # edit the gpsd settings file

    • change DEVICES="" to DEVICES="/dev/ttyUSB0" # /dev name may be different

    • save and quit gedit


    • sudo systemctl restart gpsd # restart gpsd




gpsmon, cgps, and xgps will now work properly.






share|improve this answer


























  • 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
    5 hours ago











  • @vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.

    – heynnema
    4 hours ago











  • @vidarlo please consider reversing your down vote. Thanks!

    – heynnema
    4 hours ago











  • 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
    4 hours ago













  • @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
    4 hours ago
















2















  • open TCP port 2947 in your firewall (if you wish other network clients access)

  • make sure your username is in group dialout

  • in terminal, edit /etc/default/gpsd



    • sudo -H gedit /etc/default/gpsd # edit the gpsd settings file

    • change DEVICES="" to DEVICES="/dev/ttyUSB0" # /dev name may be different

    • save and quit gedit


    • sudo systemctl restart gpsd # restart gpsd




gpsmon, cgps, and xgps will now work properly.






share|improve this answer


























  • 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
    5 hours ago











  • @vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.

    – heynnema
    4 hours ago











  • @vidarlo please consider reversing your down vote. Thanks!

    – heynnema
    4 hours ago











  • 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
    4 hours ago













  • @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
    4 hours ago














2












2








2








  • open TCP port 2947 in your firewall (if you wish other network clients access)

  • make sure your username is in group dialout

  • in terminal, edit /etc/default/gpsd



    • sudo -H gedit /etc/default/gpsd # edit the gpsd settings file

    • change DEVICES="" to DEVICES="/dev/ttyUSB0" # /dev name may be different

    • save and quit gedit


    • sudo systemctl restart gpsd # restart gpsd




gpsmon, cgps, and xgps will now work properly.






share|improve this answer
















  • open TCP port 2947 in your firewall (if you wish other network clients access)

  • make sure your username is in group dialout

  • in terminal, edit /etc/default/gpsd



    • sudo -H gedit /etc/default/gpsd # edit the gpsd settings file

    • change DEVICES="" to DEVICES="/dev/ttyUSB0" # /dev name may be different

    • save and quit gedit


    • sudo systemctl restart gpsd # restart gpsd




gpsmon, cgps, and xgps will now work properly.







share|improve this answer














share|improve this answer



share|improve this answer








edited 3 hours ago

























answered 5 hours ago









heynnemaheynnema

19.6k22158




19.6k22158













  • 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
    5 hours ago











  • @vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.

    – heynnema
    4 hours ago











  • @vidarlo please consider reversing your down vote. Thanks!

    – heynnema
    4 hours ago











  • 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
    4 hours ago













  • @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
    4 hours ago



















  • 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
    5 hours ago











  • @vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.

    – heynnema
    4 hours ago











  • @vidarlo please consider reversing your down vote. Thanks!

    – heynnema
    4 hours ago











  • 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
    4 hours ago













  • @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
    4 hours ago

















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
5 hours ago





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
5 hours ago













@vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.

– heynnema
4 hours ago





@vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.

– heynnema
4 hours ago













@vidarlo please consider reversing your down vote. Thanks!

– heynnema
4 hours ago





@vidarlo please consider reversing your down vote. Thanks!

– heynnema
4 hours ago













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
4 hours ago







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
4 hours ago















@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
4 hours ago





@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
4 hours ago










Geoffrey-c is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Geoffrey-c is a new contributor. Be nice, and check out our Code of Conduct.













Geoffrey-c is a new contributor. Be nice, and check out our Code of Conduct.












Geoffrey-c is a new contributor. Be nice, and check out our Code of Conduct.
















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.




draft saved


draft discarded














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





















































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







Popular posts from this blog

Szabolcs (Ungheria) Altri progetti | Menu di navigazione48°10′14.56″N 21°29′33.14″E /...

Discografia di Klaus Schulze Indice Album in studio | Album dal vivo | Singoli | Antologie | Colonne...

How to make inet_server_addr() return localhost in spite of ::1/128RETURN NEXT in Postgres FunctionConnect to...