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

NAME

6       urxvt256c-mld - urxvt256c-ml terminal daemon
7

SYNOPSIS

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

DESCRIPTION

14       This manpage describes the urxvt256c-mld daemon, which is the same
15       vt102 terminal emulator as urxvt256c-ml, but runs as a daemon that can
16       open 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 urxvt256c-ml daemon include faster creation
23       time 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 urxvt256c-mld
29       instance including all windows it has opened.
30

OPTIONS

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

EXAMPLES

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

ENVIRONMENT

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

SEE ALSO

91       urxvt256c-ml(7), urxvt256c-mlc(1)
92
93
94
959.12                              2011-06-29                   urxvt256c-ml(1)
Impressum