1urxvt(1) RXVT-UNICODE urxvt(1)
2
6 urxvtd - urxvt terminal daemon
7
9 urxvtd [-q|--quiet] [-o|--opendisplay] [-f|--fork] [-m|--mlock]
10 [-e|--eval perlstring]
11 urxvtd -q -o -f # for .xsession use
13
15 This manpage describes the urxvtd daemon, which is the same vt102
16 terminal emulator as urxvt, but runs as a daemon that can open multiple
17 terminal windows within the same process.
18 You can run it from your X startup scripts, for example, although it is
20 not dependent on a working DISPLAY and, in fact, can open windows on
21 multiple X displays on the same time.
22 Advantages of running a urxvt daemon include faster creation time for
24 terminal windows and a lot of saved memory.
25 The disadvantage is a possible impact on stability - if the main
27 program crashes, all processes in the terminal windows are terminated.
28 For example, as there is no way to cleanly react to abnormal connection
29 closes, "xkill" and server resets/restarts will kill the urxvtd
30 instance including all windows it has opened.
31
33 urxvtd currently understands a few options only. Bundling of options is
34 not yet supported.
35 -q, --quiet
37 Normally, urxvtd outputs the message "rxvt-unicode daemon listening
38 on <path>" after binding to its control socket. This option will
39 suppress this message (errors and warnings will still be logged).
40 -o, --opendisplay
42 This forces urxvtd to open a connection to the current $DISPLAY and
43 keep it open.
44 This is useful if you want to bind an instance of urxvtd to the
46 lifetime of a specific display/server. If the server does a reset,
47 urxvtd will be killed automatically.
48 -f, --fork
50 This makes urxvtd fork after it has bound itself to its control
51 socket.
52 -m, --mlock
54 This makes urxvtd call mlockall(2) on itself. This locks urxvtd in
55 RAM and prevents it from being swapped out to disk, at the cost of
56 consuming a lot more memory on most operating systems.
57 Note: In order to use this feature, your system administrator must
59 have set your user's RLIMIT_MEMLOCK to a size greater than or equal
60 to the size of the urxvtd binary (or to unlimited). See
61 /etc/security/limits.conf.
62 Note 2: There is a known bug in glibc (possibly fixed in 2.8 and
64 later versions) where calloc returns non-zeroed memory when
65 mlockall is in effect. If you experience crashes or other odd
66 behaviour while using --mlock, try it without it.
67 -e, --eval perlstring
69 Evaluate the given perl code after basic initialisation (requires
70 perl support to be enabled when compiling urxvtd).
71 This can be used for example to configure the internal perl
73 interpreter, which is shared between all terminal instances, or
74 create additional listening sockets for additional protocols.
75 The code is currently executed before creating the normal listening
77 sockets: this might change in future versions.
78
80 This is a useful invocation of urxvtd in a .xsession-style script:
81 urxvtd -q -f -o
83 This waits till the control socket is available, opens the current
85 display and forks into the background. When you log-out, the server is
86 reset and urxvtd is killed.
87
89 RXVT_SOCKET
90 Both urxvtc and urxvtd use the environment variable RXVT_SOCKET to
91 create a listening socket and to contact the urxvtd, respectively.
92 If the variable is missing then $HOME/.urxvt/urxvtd-<nodename> is
93 used.
94 LISTEN_PID, LISTEN_FDS, LISTEN_FDNAMES
96 if these environment variables are set, urxvtd checks for a file
97 descriptor passed by the service manager via systemd native
98 interface. If one is provided, urxvtd uses it as its listening
99 socket instead of creating one as specified above.
100 DISPLAY
102 Only used when the "--opendisplay" option is specified. Must
103 contain a valid X display name.
104
106 urxvt(7), urxvtc(1)
1079.31 2023-01-02 urxvt(1)