2011-12-10 06:27:40 -05:00
|
|
|
i3-dump-log(1)
|
|
|
|
|
==============
|
2013-09-21 18:08:27 -04:00
|
|
|
Michael Stapelberg <michael@i3wm.org>
|
|
|
|
|
v4.6, September 2013
|
2011-12-10 06:27:40 -05:00
|
|
|
|
|
|
|
|
== NAME
|
|
|
|
|
|
|
|
|
|
i3-dump-log - dumps the i3 SHM log
|
|
|
|
|
|
|
|
|
|
== SYNOPSIS
|
|
|
|
|
|
2013-09-21 18:08:27 -04:00
|
|
|
i3-dump-log [-s <socketpath>] [-f]
|
2011-12-10 06:27:40 -05:00
|
|
|
|
|
|
|
|
== DESCRIPTION
|
|
|
|
|
|
|
|
|
|
Debug versions of i3 automatically use 1% of your RAM (but 25 MiB max) to store
|
2012-07-21 18:16:52 -04:00
|
|
|
full debug log output. This is extremely helpful for bugreports and
|
2011-12-10 06:27:40 -05:00
|
|
|
figuring out what is going on, without permanently logging to a file.
|
|
|
|
|
|
|
|
|
|
With i3-dump-log, you can dump the SHM log to stdout.
|
|
|
|
|
|
2013-09-21 18:08:27 -04:00
|
|
|
The -f flag works like tail -f, i.e. the process does not terminate after
|
|
|
|
|
dumping the log, but prints new lines as they appear.
|
|
|
|
|
|
2011-12-10 06:27:40 -05:00
|
|
|
== EXAMPLE
|
|
|
|
|
|
|
|
|
|
i3-dump-log | gzip -9 > /tmp/i3-log.gz
|
|
|
|
|
|
|
|
|
|
== SEE ALSO
|
|
|
|
|
|
|
|
|
|
i3(1)
|
|
|
|
|
|
|
|
|
|
== AUTHOR
|
|
|
|
|
|
|
|
|
|
Michael Stapelberg and contributors
|
