1urxvt(1) RXVT-UNICODE urxvt(1)
2
6 urxvtd - urxvt terminal daemon
7
9 urxvtd [-q|--quiet] [-o|--opendisplay] [-f|--fork] [-m|--mlock]
10 urxvtd -q -o -f # for .xsession use
12
14 This manpage describes the urxvtd daemon, which is the same vt102
15 terminal emulator as urxvt, but runs as a daemon that can open multiple
16 terminal windows within the same process.
17 You can run it from your X startup scripts, for example, although it is
19 not dependent on a working DISPLAY and, in fact, can open windows on
20 multiple X displays on the same time.
21 Advantages of running a urxvt daemon include faster creation time for
23 terminal windows and a lot of saved memory.
24 The disadvantage is a possible impact on stability - if the main
26 program crashes, all processes in the terminal windows are terminated.
27 For example, as there is no way to cleanly react to abnormal connection
28 closes, "xkill" and server resets/restarts will kill the urxvtd
29 instance including all windows it has opened.
30
32 urxvtd currently understands a few options only. Bundling of options is
33 not yet supported.
34 -q, --quiet
36 Normally, urxvtd outputs the message "rxvt-unicode daemon listening
37 on <path>" after binding to its control socket. This option will
38 suppress this message (errors and warnings will still be logged).
39 -o, --opendisplay
41 This forces urxvtd to open a connection to the current $DISPLAY and
42 keep it open.
43 This is useful if you want to bind an instance of urxvtd to the
45 lifetime of a specific display/server. If the server does a reset,
46 urxvtd will be killed automatically.
47 -f, --fork
49 This makes urxvtd fork after it has bound itself to its control
50 socket.
51 -m, --mlock
53 This makes urxvtd call mlockall(2) on itself. This locks urxvtd in
54 RAM and prevents it from being swapped out to disk, at the cost of
55 consuming a lot more memory on most operating systems.
56 Note: In order to use this feature, your system administrator must
58 have set your user's RLIMIT_MEMLOCK to a size greater than or equal
59 to the size of the urxvtd binary (or to unlimited). See
60 /etc/security/limits.conf.
61 Note 2: There is a known bug in glibc (possibly fixed in 2.8 and
63 later versions) where calloc returns non-zeroed memory when
64 mlockall is in effect. If you experience crashes or other odd
65 behaviour while using --mlock, try it without it.
66
68 This is a useful invocation of urxvtd in a .xsession-style script:
69 urxvtd -q -f -o
71 This waits till the control socket is available, opens the current
73 display and forks into the background. When you log-out, the server is
74 reset and urxvtd is killed.
75
77 RXVT_SOCKET
78 Both urxvtc and urxvtd use the environment variable RXVT_SOCKET to
79 create a listening socket and to contact the urxvtd, respectively.
80 If the variable is missing then $HOME/.rxvt-unicode-<nodename> is
81 used.
82 DISPLAY
84 Only used when the "--opendisplay" option is specified. Must
85 contain a valid X display name.
86
88 urxvt(7), urxvtc(1)
899.12 2011-06-29 urxvt(1)