1urxvt-ml(1) RXVT-UNICODE urxvt-ml(1)
2
6 urxvt-mld - urxvt-ml terminal daemon
7
9 urxvt-mld [-q|--quiet] [-o|--opendisplay] [-f|--fork] [-m|--mlock]
10 [-e|--eval perlstring]
11 urxvt-mld -q -o -f # for .xsession use
13
15 This manpage describes the urxvt-mld daemon, which is the same vt102
16 terminal emulator as urxvt-ml, but runs as a daemon that can open
17 multiple 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-ml daemon include faster creation time
24 for 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 urxvt-mld
30 instance including all windows it has opened.
31
33 urxvt-mld currently understands a few options only. Bundling of options
34 is not yet supported.
35 -q, --quiet
37 Normally, urxvt-mld outputs the message "rxvt-unicode daemon
38 listening on <path>" after binding to its control socket. This
39 option will suppress this message (errors and warnings will still
40 be logged).
41 -o, --opendisplay
43 This forces urxvt-mld to open a connection to the current $DISPLAY
44 and keep it open.
45 This is useful if you want to bind an instance of urxvt-mld to the
47 lifetime of a specific display/server. If the server does a reset,
48 urxvt-mld will be killed automatically.
49 -f, --fork
51 This makes urxvt-mld fork after it has bound itself to its control
52 socket.
53 -m, --mlock
55 This makes urxvt-mld call mlockall(2) on itself. This locks urxvt-
56 mld in RAM and prevents it from being swapped out to disk, at the
57 cost of consuming a lot more memory on most operating systems.
58 Note: In order to use this feature, your system administrator must
60 have set your user's RLIMIT_MEMLOCK to a size greater than or equal
61 to the size of the urxvt-mld binary (or to unlimited). See
62 /etc/security/limits.conf.
63 Note 2: There is a known bug in glibc (possibly fixed in 2.8 and
65 later versions) where calloc returns non-zeroed memory when
66 mlockall is in effect. If you experience crashes or other odd
67 behaviour while using --mlock, try it without it.
68 -e, --eval perlstring
70 Evaluate the given perl code after basic initialisation (requires
71 perl support to be enabled when compiling urxvt-mld).
72 This can be used for example to configure the internal perl
74 interpreter, which is shared between all terminal instances, or
75 create additional listening sockets for additional protocols.
76 The code is currently executed before creating the normal listening
78 sockets: this might change in future versions.
79
81 This is a useful invocation of urxvt-mld in a .xsession-style script:
82 urxvt-mld -q -f -o
84 This waits till the control socket is available, opens the current
86 display and forks into the background. When you log-out, the server is
87 reset and urxvt-mld is killed.
88
90 RXVT_SOCKET
91 Both urxvt-mlc and urxvt-mld use the environment variable
92 RXVT_SOCKET to create a listening socket and to contact the urxvt-
93 mld, respectively. If the variable is missing then
94 $HOME/.urxvt/urxvtd-<nodename> is used.
95 DISPLAY
97 Only used when the "--opendisplay" option is specified. Must
98 contain a valid X display name.
99
101 urxvt-ml(7), urxvt-mlc(1)
1029.22 2016-01-23 urxvt-ml(1)