More than half of all files here are *~ files:
bor@opensuse:~/src/systemd> ls -1
/var/log/journal/40527be2480f8cf60f4e8d4b06b0/*~ | wc -l
85
bor@opensuse:~/src/systemd> ls -1
/var/log/journal/40527be2480f8cf60f4e8d4b06b0/* | wc -l
127
If I understand it correctly they are corrupted file
On Fri, Aug 07, 2015 at 11:53:13AM +0200, Sebastian Schindler wrote:
> Grep-ing seems to be the only solution to find log entries if you don't fully
> know what you're looking for. For example: You want to see all entries
> containing a certain MESSAGE that gets enriched with additional information
On 2015-08-07 11:53, Sebastian Schindler wrote:
> Hi all.
>
> The journal format offers powerful filter capabilities. Unfortunately this
> power
> is lost, if you have to use grep to find certain information.
> Example given (unscientific benchmark), count the number of entries for a
> (known) ex
Dear All,
If someone would be so kind to show me a way to completely wipe out one display
number of a TigerVNC setup in Centos 7 without setting up the entire system
from scratch, that would be very helpful.
Regards,
Michael
-Ursprüngliche Nachricht-
Von: Prof. Dr. Michael Schefczyk
