INPUTLIRCD(8)

👑 INPUTLIRCD(8) — the inputlircd manual page, bestie edition 💅

okay so you found inputlircd in section 8 of the manual and you want the ✨vibes✨ version? say less. this is the whole page, nothing skipped, nothing invented, just with the personality it deserved all along 🫶

---

🌸 NAME 🌸

inputlircd — a zeroconf LIRC daemon that runs on input event devices 💖

---

✨ SYNOPSIS ✨

inputlircd [-d socket] [-f] [-c] [-r repeat-rate] [-g] [-m keycode]
           [-n device name] [-u username] [-t path] [-N rc name] device
           [device ...]

like yes she takes arguments, and yes she's picky about them. icon behaviour tbh 👑

---

🦋 DESCRIPTION 🦋

so inputlircd is this small LIRC daemon that reads from /dev/input/eventX devices and yeets the keycodes it receives over to whatever LIRC clients are connecting in. no cap, that's the whole job. 🎀

and the best part? she needs zero configuration. literally none. she just uses the standardised names for the keycodes, the same ones the kernel already uses. the way that so many USB remote controls that show up as HID devices — plus multimedia keyboards — just work out of the box?? obsessed. 🔥

she does expect one thing though: a list of input event devices as commandline parameters. and she will only read events from those devices. she's loyal like that. no stray reads. 🙈

---

💖 OPTIONS 💖

• -d socket — where the UNIX socket lives, the one LIRC clients connect to. default is /run/lirc/lircd. ✨
• -f — run in the foreground. no vanishing into the background on you, she stays right there. 👀
• -c — capture modifier keys. this makes CTRL, SHIFT, ALT and META act as modifier keys: when you press them together with another key, they change the LIRC event for that other key instead of being sent as their own separate LIRC events. combo energy. 💅
• -r repeat-rate — set the repeat rate of the remote control, in milliseconds. default is 0. repeated keys that arrive less than repeat-rate milliseconds apart get flagged as repeat LIRC events. so close together they're basically holding hands. 🥺
• -g — grab the input device(s). this gives inputlircd exclusive access to the input devices and stops events from propagating any further. she's not sharing, bestie. 🚫
• -m keycode — minimum keycode to send to LIRC clients. anything lower than this number gets filtered out. default is 88, which filters out the alphanumeric section and the keypad section of normal keyboards, but lets all the extended keys through. the rationale? clients should not be able to grab normal keypresses, because that could be a security risk. so like, protect yourself. 🛡️
• -n device name — the name of an input device to read events from. this scans all the available input event devices, and if the symbolic name of an event device matches device name, it gets added to the list of devices to read from. device name can contain wildcard patterns — peep glob(7). want a list of available devices and their names? cat /proc/bus/input/devices or use lsinput(8). 🌈
• -u username — set the user and group id to that of username, after opening the devices and the UNIX socket as root. default is nobody. drop the privileges, stay humble. 🧚
• -t path — gives the path to a file holding a mapping between input event key names and the commands that should be reported via lirc. the files should contain lines of the form KEY_FOO = bar. useful for backward compatibility. default is not to use a translation table at all. 🍓
• -N rc name — set the remote control name, aka the value of the last field of LIRC broadcast messages. if there's more than one input event device, the name you give gets used for all of them. if rc name isn't specified, the filesystem path of each input event device is used as its remote control name. ✨
• device — one or more input event devices. if you want inputlircd to process the multimedia keys on your keyboard, then /dev/input/event0 is the most likely choice. got other input devices, like USB remote controllers that act like a HID device? then you probably need one of the other event devices that are present. check /proc/bus/input/devices for a list of available input devices. and if you're unsure — just add all the available input event devices. go big, honestly. 💀

---

🎀 FILES 🎀

• /run/lirc/lircd — the default location of the UNIX socket that LIRC clients connect to. 💜
• /dev/input/eventX — the kernel input layer's event device files. 🌸
• /proc/bus/input/devices — the list of all input devices. 📋

---

🔥 SEE ALSO 🔥

irw(1), input-events(8), setkeycodes(8), /usr/include/linux/input-event-codes.h.

like go read those too, they're the friend group. 💅

---

and that's the whole page bestie, no crumbs left behind 🫶 this was Mon, 06 Feb 2006 17:42:25 +0100 — vintage, iconic, still serving. mwah 💋