Difference between revisions of "Limit the size of .log files & the journal"

Limit the size of .log files & the journal (view source)

6 bytes removed , 7 years ago

no edit summary

Anonymous user

@@ Line 35: / Line 35: @@
 <br clear="all"/>
-=Read this first its important=
+= The journal & the logs duplicate the same information =
+You can read the text of the log files in a text editor, or using the '''cat''', '''more''', '''less''' & such commands as you would on any other text file. The journal on the other hand requires the '''journalctl''' command to be able to access its contents. The following is a good way to read the journal:
+ sudo journalctl
+<br clear="all"/>
+=Read this its important=
   Note: '''etc/systemd/journald.conf.d/*.conf'''
@@ Line 54: / Line 62: @@
 What that means is that you can create configuration files '''.conf''' in the '''/etc/systemd/journald.conf.d/''' directory, with suitable names of your choice. The content of these files take precedence over any other settings or configurations in systemd. Please bear that in mind when you read the following? In my cumbersome way I've tried to make it all too obvious...
-<br clear="all"/>
-= The journal & the logs duplicate the same information =
-You can read the text of the log files in a text editor, or using the '''cat''', '''more''', '''less''' & such commands as you would on any other text file. The journal on the other hand requires the '''journalctl''' command to be able to access its contents. The following is a good way to read the journal:
- sudo journalctl
 <br clear="all"/>