Those many factors customer support must think of in advance

[OpenSourcerer 1435]

1 hour ago, Staff said:

sudo journalctl | grep bluetit

Useless use of a pipe. Comparable to cat file.txt | grep something.

# journalctl -u bluetit.service

The exact firewall output would be nice, too. If the local network is unreachable, either a route is missing or NetLock interferes.

[Staff 9972]

4 hours ago, OpenSourcerer said:

Useless use of a pipe. Comparable to cat file.txt | grep something.

# journalctl -u bluetit.service 

Hello!

Nope, there's a big difference, at least for customer support personnel. 😀

journalctl -u option by default will force the user to press <SPACE> etc. to reach the end of the log or "q" to exit prematurely or the <END> key cutting out parts of the log.

Any combo of the above has translated (and will again translate sooner or later) into users sending us only pieces of log. We could ask the user to re-direct the output to a file, then find the file, print it or open it with a text viewer, copy and paste its content on the next msg but why? It is additional work that's not really needed.

We can save anyway piping and make you happier with

< <(sudo journalctl) grep bluetit

Quote

The exact firewall output would be nice, too. If the local network is unreachable, either a route is missing or NetLock interferes.

It seems that @bulbous_blues is in a subnet inside 192.168.0.0/16 which Bluetit always sets completely open in input and output, both with iptables[-legacy} and nftables. Can you confirm @bulbous_blues ?

Kind regards

[OpenSourcerer 1435]

# journalctl -eu bluetit.service

to jump to the end.

# journalctl -g <pattern>

to grep the journal <- 1:1 the definition of "useless use of journalctl | grep x".

# journalctl -b -1 -u bluetit.service

to view Bluetit log output from current boot (0) or the one before (-1).
 

13 minutes ago, Staff said:

< <(sudo journalctl) grep bluetit

Now that's reducing the useless use of Shell functions to absurdity…

[Staff 9972]

Quote

journalctl -eu bluetit.service 

Nope, that prints only the last 18-19 lines in most versions. Insufficient.
 

Quote

journalctl -g <pattern>

Nope, that's not supported in various journalctl versions, including the default version in openSUSE 15.2 (latest release) and many other distributions.
 

Quote

journalctl -b -1 -u bluetit.service

Nope, that requires persistent journal. Disabled by default in many, maybe most, distributions.
   

Quote

Now that's reducing the useless use of Shell functions to absurdity…

Nope, that's very rudimentary re-direction in bash and other interpreters. Bash functions are a totally different thing. If you think that a rudimentary re-direction is an "absurd shell function", maybe UNIX shells are not for you. Try Windows PowerShell. <evil grin>

Kind regards