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

NAME

6       urxvt256cd - urxvt256c terminal daemon
7

SYNOPSIS

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

DESCRIPTION

14       This manpage describes the urxvt256cd daemon, which is the same vt102
15       terminal emulator as urxvt256c, 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 urxvt256c 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 urxvt256cd
29       instance including all windows it has opened.
30

OPTIONS

32       urxvt256cd currently understands a few options only. Bundling of
33       options is not yet supported.
34
35       -q, --quiet
36           Normally, urxvt256cd 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 urxvt256cd 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 urxvt256cd to the
46           lifetime of a specific display/server. If the server does a reset,
47           urxvt256cd will be killed automatically.
48
49       -f, --fork
50           This makes urxvt256cd fork after it has bound itself to its control
51           socket.
52
53       -m, --mlock
54           This makes urxvt256cd call mlockall(2) on itself. This locks
55           urxvt256cd in RAM and prevents it from being swapped out to disk,
56           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 urxvt256cd 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 urxvt256cd in a .xsession-style script:
71
72          urxvt256cd -q -f -o
73
74       This waits till the control socket is available, opens the current
75       display and forks into the background. When you log-out, the server is
76       reset and urxvt256cd is killed.
77

ENVIRONMENT

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

SEE ALSO

90       urxvt256c(7), urxvt256cc(1)
91
92
93
949.12                              2011-06-29                      urxvt256c(1)
Impressum