3 Michael Stapelberg <michael@i3wm.org>
8 i3status - Generates a status line for dzen2 or xmobar
12 i3status [-c configfile] [-h] [-v]
17 Specifies an alternate configuration file path. By default, i3status looks for
18 configuration files in the following order:
21 2. ~/.config/i3status/config (or $XDG_CONFIG_HOME/i3status/config if set)
23 4. /etc/xdg/i3status/config (or $XDG_CONFIG_DIRS/i3status/config if set)
27 i3status is a small program (about 1500 SLOC) for generating a status bar for
28 i3bar, dzen2, xmobar or similar programs. It is designed to be very
29 efficient by issuing a very small number of system calls, as one generally
30 wants to update such a status line every second. This ensures that even under
31 high load, your status bar is updated correctly. Also, it saves a bit of energy
32 by not hogging your CPU as much as spawning the corresponding amount of shell
37 The basic idea of i3status is that you can specify which "modules" should
38 be used (the order directive). You can then configure each module with its
39 own section. For every module, you can specify the output format. See below
40 for a complete reference.
43 -------------------------------------------------------------
45 output_format = "dzen2"
52 order += "run_watch DHCP"
53 order += "run_watch VPN"
54 order += "wireless wlan0"
55 order += "ethernet eth0"
57 order += "cpu_temperature 0"
59 order += "tztime local"
60 order += "tztime berlin"
63 format_up = "W: (%quality at %essid, %bitrate) %ip"
64 format_down = "W: down"
68 # if you use %speed, i3status requires the cap_net_admin capability
69 format_up = "E: %ip (%speed)"
70 format_down = "E: down"
74 format = "%status %percentage %remaining %emptytime"
75 path = "/sys/class/power_supply/BAT%d/uevent"
80 pidfile = "/var/run/dhclient*.pid"
84 pidfile = "/var/run/vpnc/pid"
88 format = "%Y-%m-%d %H:%M:%S"
92 format = "%Y-%m-%d %H:%M:%S %Z"
93 timezone = "Europe/Berlin"
101 format = "T: %degrees °C"
102 path = "/sys/devices/platform/coretemp.0/temp1_input"
108 -------------------------------------------------------------
112 The +colors+ directive will disable all colors if you set it to +false+. You can
113 also specify the colors that will be used to display "good", "degraded" or "bad"
114 values using the +color_good+, +color_degraded+ or +color_bad+ directives,
115 respectively. Those directives are only used if color support is not disabled by
116 the +colors+ directive. The input format for color values is the canonical RGB
117 hexadecimal triplet (with no separators between the colors), prefixed by a hash
120 *Example configuration*:
121 -------------------------------------------------------------
122 color_good = "#00FF00"
123 -------------------------------------------------------------
125 Likewise, you can use the +color_separator+ directive to specify the color that
126 will be used to paint the separator bar. The separator is always output in
127 color, even when colors are disabled by the +colors+ directive.
129 The +interval+ directive specifies the time in seconds for which i3status will
130 sleep before printing the next status line.
132 Using +output_format+ you can chose which format strings i3status should
133 use in its output. Currently available are:
136 i3bar comes with i3 and provides a workspace bar which does the right thing in
137 multi-monitor situations. It also comes with tray support and can display the
138 i3status output. This output type uses JSON to pass as much meta-information to
139 i3bar as possible (like colors, which blocks can be shortened in which way,
142 Dzen is a general purpose messaging, notification and menuing program for X11.
143 It was designed to be scriptable in any language and integrate well with window
144 managers like dwm, wmii and xmonad though it will work with any windowmanger
146 xmobar is a minimalistic, text based, status bar. It was designed to work
147 with the xmonad Window Manager.
149 Does not use any color codes. Separates values by the pipe symbol. This should
150 be used with i3bar and can be used for custom scripts.
152 It's also possible to use the color_good, color_degraded, color_bad directives
153 to define specific colors per module. If one of these directives is defined
154 in a module section its value will override the value defined in the general
155 section just for this module.
159 This module gets the IPv6 address used for outgoing connections (that is, the
160 best available public IPv6 address on your computer).
162 *Example format_up*: +%ip+
164 *Example format_down* +no IPv6+
168 Gets used, free, available and total amount of bytes on the given mounted filesystem.
170 These values can also be expressed in percentages with the percentage_used,
171 percentage_free, percentage_avail and percentage_used_of_avail formats.
173 *Example order*: +disk /mnt/usbstick+
175 *Example format*: +%free (%avail)/ %total+
177 *Example format*: +%percentage_used used, %percentage_free free, %percentage_avail avail+
181 Expands the given path to a pidfile and checks if the process ID found inside
182 is valid (that is, if the process is running). You can use this to check if
183 a specific application, such as a VPN client or your DHCP client is running.
185 *Example order*: +run_watch DHCP+
187 *Example format*: +%title: %status+
191 Gets the link quality and ESSID of the given wireless network interface. You
192 can specify different format strings for the network being connected or not
195 *Example order*: +wireless wlan0+
197 *Example format*: +W: (%quality at %essid, %bitrate) %ip+
201 Gets the IP address and (if possible) the link speed of the given ethernet
202 interface. Getting the link speed requires the cap_net_admin capability. Set
203 it using +setcap cap_net_admin=ep $(which i3status)+.
205 *Example order*: +ethernet eth0+
207 *Example format*: +E: %ip (%speed)+
211 Gets the status (charging, discharging, running), percentage, remaining
212 time and power consumption (in Watts) of the given battery and when it's
213 estimated to be empty. If you want to use the last full capacity instead of the
214 design capacity (when using the design capacity, it may happen that your
215 battery is at 23% when fully charged because it’s old. In general, I want to
216 see it this way, because it tells me how worn off my battery is.), just specify
217 +last_full_capacity = true+.
219 If you want the battery percentage to be shown without decimals, add
220 +integer_battery_capacity = true+.
222 If your battery is represented in a non-standard path in /sys, be sure to
223 modify the "path" property accordingly. The first occurence of %d gets replaced
224 with the battery number, but you can just hard-code a path as well.
226 It is possible to define a low_threshold that causes the battery text to be
227 colored red. The low_threshold type can be of threshold_type "time" or
228 "percentage". So, if you configure low_threshold to 10 and threshold_type to
229 "time", and your battery lasts another 9 minutes, it will be colored red.
231 *Example order*: +battery 0+
233 *Example format*: +%status %remaining (%emptytime %consumption)+
235 *Example low_threshold*: +30+
237 *Example threshold_type*: +time+
241 Gets the temperature of the given thermal zone. It is possible to
242 define a max_threshold that will color the temperature red in case the
243 specified thermal zone is getting too hot. Defaults to 75 degrees C.
245 *Example order*: +cpu_temperature 0+
247 *Example format*: +T: %degrees °C+
249 *Example max_threshold*: +42+
253 Gets the percentual CPU usage from +/proc/stat+ (Linux) or +sysctl(3)+ (FreeBSD/OpenBSD).
255 *Example order*: +cpu_usage+
257 *Example format*: +%usage+
261 Gets the system load (number of processes waiting for CPU time in the last
262 1, 5 and 15 minutes). It is possible to define a max_threshold that will
263 color the load value red in case the load average of the last minute is
264 getting higher than the configured threshold. Defaults to 5.
266 *Example order*: +load+
268 *Example format*: +%1min %5min %15min+
270 *Example max_threshold*: 5
274 Outputs the current time in the local timezone.
275 To use a different timezone, you can set the TZ environment variable,
276 or use the +tztime+ module.
277 See +strftime(3)+ for details on the format string.
279 *Example order*: +time+
281 *Example format*: +%Y-%m-%d %H:%M:%S+
285 Outputs the current time in the given timezone.
286 If no timezone is given, local time will be used.
287 See +strftime(3)+ for details on the format string.
288 The system's timezone database is usually installed in +/usr/share/zoneinfo+.
289 Files below that path make for valid timezone strings, e.g. for
290 +/usr/share/zoneinfo/Europe/Berlin+ you can set timezone to +Europe/Berlin+
291 in the +tztime+ module.
293 *Example order*: +tztime berlin+
295 *Example format*: +%Y-%m-%d %H:%M:%S %Z+
297 *Example timezone*: +Europe/Berlin+
301 Outputs the current discordian date in user-specified format. See +ddate(1)+ for
302 details on the format string.
303 *Note*: Neither *%.* nor *%X* are implemented yet.
305 *Example order*: +ddate+
307 *Example format*: +%{%a, %b %d%}, %Y%N - %H+
311 Outputs the volume of the specified mixer on the specified device. Works only
312 on Linux because it uses ALSA.
313 A simplified configuration can be used on FreeBSD and OpenBSD due to
314 the lack of ALSA, the +device+, +mixer+ and +mixder_idx+ options can be
315 ignored on these systems. On these systems the OSS API is used instead to
316 query +/dev/mixer+ directly.
318 *Example order*: +volume master+
320 *Example format*: +♪: %volume+
322 *Example configuration*:
323 -------------------------------------------------------------
325 format = "♪: %volume"
330 -------------------------------------------------------------
332 == Using i3status with dzen2
334 After installing dzen2, you can directly use it with i3status. Just ensure that
335 +output_format+ is set to +dzen2+.
337 *Example for usage of i3status with dzen2*:
338 --------------------------------------------------------------
339 i3status | dzen2 -fg white -ta r -w 1280 \
340 -fn "-misc-fixed-medium-r-normal--13-120-75-75-C-70-iso8859-1"
341 --------------------------------------------------------------
343 == Using i3status with xmobar
345 To get xmobar to start, you might need to copy the default configuration
346 file to +~/.xmobarrc+. Also, ensure that the +output_format+ option for i3status
349 *Example for usage of i3status with xmobar*:
350 ---------------------------------------------------------------------
351 i3status | xmobar -o -t "%StdinReader%" -c "[Run StdinReader]"
352 ---------------------------------------------------------------------
354 == What about memory usage or CPU frequency?
356 While talking about two specific things, please understand this section as a
357 general explanation why your favorite information is not included in i3status.
359 Let’s talk about memory usage specifically. It is hard to measure memory in a
360 way which is accurate or meaningful. An in-depth understanding of how paging
361 and virtual memory work in your operating system is required. Furthermore, even
362 if we had a well-defined way of displaying memory usage and you would
363 understand it, I think that it’s not helpful to repeatedly monitor your memory
364 usage. One reason for that is that I have not run out of memory in the last few
365 years. Memory has become so cheap that even in my 4 year old notebook, I have
366 8 GiB of RAM. Another reason is that your operating system will do the right
367 thing anyway: Either you have not enough RAM for your workload, but you need to
368 do it anyway, then your operating system will swap. Or you don’t have enough
369 RAM and you want to restrict your workload so that it fits, then the operating
370 system will kill the process using too much RAM and you can act accordingly.
372 For CPU frequency, the situation is similar. Many people don’t understand how
373 frequency scaling works precisely. The generally recommended CPU frequency
374 governor ("ondemand") changes the CPU frequency far more often than i3status
375 could display it. The display number is therefore often incorrect and doesn’t
376 tell you anything useful either.
378 In general, i3status wants to display things which you would look at
379 occasionally anyways, like the current date/time, whether you are connected to
380 a WiFi network or not, and if you have enough disk space to fit that 4.3 GiB
383 However, if you need to look at some kind of information more than once in a
384 while (like checking repeatedly how full your RAM is), you are probably better
385 off with a script doing that, which pops up an alert when your RAM usage reaches
386 a certain threshold. After all, the point of computers is not to burden you
387 with additional boring tasks like repeatedly checking a number.
389 == External scripts/programs with i3status
391 In i3status, we don’t want to implement process management again. Therefore,
392 there is no module to run arbitrary scripts or commands. Instead, you should
393 use your shell, for example like this:
395 *Example for prepending the i3status output*:
396 --------------------------------------------------------------
398 # shell script to prepend i3status with more stuff
403 echo "mystuff | $line" || exit 1
405 --------------------------------------------------------------
407 Put that in some script, say +.bin/my_i3status.sh+ and execute that instead of i3status.
409 Note that if you want to use the JSON output format (with colors in i3bar), you
410 need to use a slightly more complex wrapper script. There are examples in the
411 contrib/ folder, see http://code.i3wm.org/i3status/tree/contrib
415 When receiving +SIGUSR1+, i3status’s nanosleep() will be interrupted and thus
416 you will force an update. You can use killall -USR1 i3status to force an update
417 after changing the system volume, for example.
421 +strftime(3)+, +date(1)+, +glob(3)+, +dzen2(1)+, +xmobar(1)+
425 Michael Stapelberg and contributors
433 Fernando Tarlá Cardoso Lemos