Logging - Revision history

Dsafonov: Add some drops about early logging

2020-02-05T12:05:05Z

Add some drops about early logging

2017-06-23T21:13:24Z

Log files: use template:opt

2017-06-23T21:11:31Z

Per-pid logs: reworded

2017-01-09T09:08:18Z

2016-09-21T09:05:36Z

2016-09-21T09:04:56Z

2016-09-16T15:16:00Z

New page

== See also ==
[[Better logging]]
[[Category:Empty articles]]

@@ Line 8: / Line 8: @@
 ; Errors
-: These show that something goes really wrong. If an error message appears on the screen CRIU doesn't complete the operation and exits with error. At the same time, if CRIU's exit code is not 0, there should be an error message. Typically there are several of them, but only the first one denotes the real obstacle CRIU has hit, all subsequent ones can be due to this first.
+: These show that something goes really wrong. If an error message appears on the screen CRIU doesn't complete the operation and exits with an error. At the same time, if CRIU's exit code is not 0, there should be an error message. Typically there are several of them, but only the first one denotes the real obstacle CRIU has hit, all subsequent ones can be due to this first.
 ; Warnings
@@ Line 49: / Line 49: @@
 Telling <code>-v0</code> will shut CRIU up, but that's really not recommended.
 == Log files ==

@@ Line 52: / Line 52: @@
 == Log files ==
-If requesting high log level you can get tons of logs on the screen. It's usually unwanted and hard to save (for further analyzes), so it's possible to ask CRIU write the logs into a log file. This is done with the option <code>-o|--log-file $name</code>. The log file will be created '''and truncated''' in the [[directories|working directory]], all messages will appear in it.
+If requesting high log level you can get tons of logs on the screen. It's usually unwanted and hard to save (for further analyzes), so it's possible to ask CRIU write the logs into a log file. This is done by {{Opt|--log-file}} option. The log file will be created '''and truncated''' in the [[directories|working directory]], all messages will appear in it.
 === Per-pid logs ===

@@ Line 56: / Line 56: @@
 === Per-pid logs ===
-During restore logs are generated by each process being restored. To make logs analyzes easier one can make CRIU generate individual log files for each process with the <code>--log-pid</code> option.
+During restore, log entries are emitted for each process being restored. To make logs analysis easier, one can make CRIU generate separate per-process log files by using {{Opt|--log-pid}} option.
 == See also ==

@@ Line 61: / Line 61: @@
 * [[Better logging]]
 * [[Directories]]
 [[Category: HOWTO]]
 [[Category: Using]]

@@ Line 39: / Line 39: @@
 pie: 39: Switched to the restorer 39                       # Message from PIE-context of process 39
 </pre>
 === Controlling the verbosity ===
@@ Line 63: / Line 62: @@
 * [[Directories]]
-[[Category:Empty articles]]
+[[Category: HOWTO]]