Using CuteCom to parse the GNSS receiver data [closed] - linux

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I used CuteCom tool to parse the GNSS receiver data in Ubuntu Desktop 20.04 LTS. In the case of not receiving satellite signals, it can generate normal data. But when I went outside to receive the signal, it generated some message except NMEA sentence. Like this:
I don't know what made this. Who can help me? Thanks in advance.

Maybe I have found why CuteCom displayed additional data. That's because the receiver will output Raw data besides NMEA sentences.

Related

Output was lost in linux terminal. How do I restore? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed last year.
Improve this question
I was executing the script and sequentially outputting the result of the execution to the command line. Since there was too much data, the output was lost, and now I only have the last part of it on the screen. Is it possible to get the whole output somehow?
No. Once the output in a terminal window is gone, you can't get it back. Therefore it's advised, either to work with a terminal that can contain more than just one screen, or to forward your output to an output file, which you can analyse afterwards.

understanding syslog logs format [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
Im geting syslogs from multiple servers, and Im having trouble to understand some syslog logs, here is one example
<189>12593340: 16596512: Jul 6 20:31:09: %PARSER-5-CFGLOG_LOGGEDCMD: User:someuser logged command:no 1480
the first number inside <> is the priority, but the two numbers after that: "12593340" and "16596512" I dont know what their are.
Does anyone knows what are those numbers?
how many formats the syslog logs has?
This is specified in the Syslog RFC:
https://www.rfc-editor.org/rfc/rfc5424#section-6.2.1
Some years ago I wrote a Shell script to calculate the numbers:
https://gist.github.com/ceving/b32d4986f43d66f252ef

Where does finger info come from in RedHat? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
One of the data elements produced by the finger command gives information on how long a logged in session has been idle. Where does finger get that information from on RedHat? I've looked in /proc/<pid>/ but did not find anything useful, and the documentation doesn't go into the commands implementation.
So, where in the system is finger (or w) pulling this information from?
The finger program get's this information from utmp file located at /var/run/utmp.

Fix microphone volume for a user [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I need to fix the microphone volume for any user in Ubuntu 16. What I want is to fix the volume, say, to %40, and keep it at that value for all times. It must be changed by no user except root. How can I do such a config? And with what tool?
Thanks.
All mixer controls of a card are managed with a single device node (/dev/snd/controlCx), so it is not possible to use file permissions for this.
However, you could program a separate tool that calls
snd_ctl_elem_lock() for the mixer control that no other program should
be able to change.

Wireshark network layer name resolution pcap [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I'm interested in saving a pcap that has network layer name resolution. While it works great within Wireshark, how can I save it with the resolved names intact? Having this information would be extremely helpful for me and save me a lot of time if this is possible. I understand in the documentation that it can't be saved within the pcap file (http://www.wireshark.org/docs/wsug_html_chunked/ChAdvNameResolutionSection.html#idp390072124) but is there an alternative way to do so? Does anyone have any solutions to this?
Thanks in advance!
I haven't tried it myself, but in theory the name resolution information can/will be stored in the pcap-ng file format, which has been Wireshark's default file format since version 1.8. The old pcap file format you cite won't, but pcap-ng has a specific defined block type in its format for ip<->name resolution information.

Resources