1urxvt-ml(1)                      RXVT-UNICODE                      urxvt-ml(1)
2
3
4

NAME

6       urxvt-mld - urxvt-ml terminal daemon
7

SYNOPSIS

9       urxvt-mld [-q|--quiet] [-o|--opendisplay] [-f|--fork] [-m|--mlock]
10
11       urxvt-mld -q -o -f    # for .xsession use
12

DESCRIPTION

14       This manpage describes the urxvt-mld daemon, which is the same vt102
15       terminal emulator as urxvt-ml, but runs as a daemon that can open
16       multiple terminal windows within the same process.
17
18       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
22       Advantages of running a urxvt-ml daemon include faster creation time
23       for terminal windows and a lot of saved memory.
24
25       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 urxvt-mld
29       instance including all windows it has opened.
30

OPTIONS

32       urxvt-mld currently understands a few options only. Bundling of options
33       is not yet supported.
34
35       -q, --quiet
36           Normally, urxvt-mld outputs the message "rxvt-unicode daemon
37           listening on <path>" after binding to its control socket. This
38           option will suppress this message (errors and warnings will still
39           be logged).
40
41       -o, --opendisplay
42           This forces urxvt-mld to open a connection to the current $DISPLAY
43           and keep it open.
44
45           This is useful if you want to bind an instance of urxvt-mld to the
46           lifetime of a specific display/server. If the server does a reset,
47           urxvt-mld will be killed automatically.
48
49       -f, --fork
50           This makes urxvt-mld fork after it has bound itself to its control
51           socket.
52
53       -m, --mlock
54           This makes urxvt-mld call mlockall(2) on itself. This locks urxvt-
55           mld in RAM and prevents it from being swapped out to disk, at the
56           cost of consuming a lot more memory on most operating systems.
57
58           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 urxvt-mld binary (or to unlimited). See
61           /etc/security/limits.conf.
62
63           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

EXAMPLES

69       This is a useful invocation of urxvt-mld in a .xsession-style script:
70
71          urxvt-mld -q -f -o
72
73       This waits till the control socket is available, opens the current
74       display and forks into the background. When you log-out, the server is
75       reset and urxvt-mld is killed.
76

ENVIRONMENT

78       RXVT_SOCKET
79           Both urxvt-mlc and urxvt-mld use the environment variable
80           RXVT_SOCKET to create a listening socket and to contact the urxvt-
81           mld, respectively. If the variable is missing then
82           $HOME/.rxvt-unicode-<nodename> is used.
83
84       DISPLAY
85           Only used when the "--opendisplay" option is specified. Must
86           contain a valid X display name.
87

SEE ALSO

89       urxvt-ml(7), urxvt-mlc(1)
90
91
92
939.12                              2011-06-29                       urxvt-ml(1)
Impressum