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