3 @@RXVT_NAME@@d - @@RXVT_NAME@@ terminal daemon
7 B<@@RXVT_NAME@@d> [-q|--quiet] [-o|--opendisplay] [-f|--fork] [-m|--mlock]
9 B<@@RXVT_NAME@@d> -q -o -f # for .xsession use
13 This manpage describes the @@RXVT_NAME@@d daemon, which is the same vt102
14 terminal emulator as @@RXVT_NAME@@, but runs as a daemon that can open
15 multiple terminal windows within the same process.
17 You can run it from your X startup scripts, for example, although it is
18 not dependent on a working DISPLAY and, in fact, can open windows on
19 multiple X displays on the same time.
21 Advantages of running a @@RXVT_NAME@@ daemon include faster creation time
22 for terminal windows and a lot of saved memory.
24 The disadvantage is a possible impact on stability - if the
25 main program crashes, all processes in the terminal windows are
26 terminated. For example, as there is no way to cleanly react to abnormal
27 connection closes, C<xkill> and server resets/restarts will kill the
28 B<@@RXVT_NAME@@d> instance including all windows it has opened.
32 B<@@RXVT_NAME@@d> currently understands a few options only. Bundling of
33 options is not yet supported.
37 =item B<-q>, B<--quiet>
39 Normally, B<@@RXVT_NAME@@d> outputs the message C<< rxvt-unicode daemon
40 listening on <path> >> after binding to its control socket. This option
41 will suppress this message (errors and warnings will still be logged).
43 =item B<-o>, B<--opendisplay>
45 This forces B<@@RXVT_NAME@@d> to open a connection to the current
46 C<$DISPLAY> and keep it open.
48 This is useful if you want to bind an instance of B<@@RXVT_NAME@@d> to
49 the lifetime of a specific display/server. If the server does a reset,
50 B<@@RXVT_NAME@@d> will be killed automatically.
52 =item B<-f>, B<--fork>
54 This makes B<@@RXVT_NAME@@d> fork after it has bound itself to its control
57 =item B<-m>, B<--mlock>
59 This makes B<@@RXVT_NAME@@d> call mlockall(2) on itself. This locks
60 B<@@RXVT_NAME@@d> in RAM and prevents it from being swapped out to disk,
61 at the cost of consuming a lot more memory on most operating systems.
63 Note: In order to use this feature, your system administrator must have set
64 your user's RLIMIT_MEMLOCK to a size greater than or equal to the size of the
65 B<@@RXVT_NAME@@d> binary (or to unlimited). See F</etc/security/limits.conf>.
67 Note 2: There is a known bug in glibc (possibly fixed in 2.8 and later
68 versions) where calloc returns non-zeroed memory when mlockall is in
69 effect. If you experience crashes or other odd behaviour while using
70 --mlock, try it without it.
76 This is a useful invocation of B<@@RXVT_NAME@@d> in a F<.xsession>-style
79 @@RXVT_NAME@@d -q -f -o
81 This waits till the control socket is available, opens the current display
82 and forks into the background. When you log-out, the server is reset and
83 B<@@RXVT_NAME@@d> is killed.
91 Both B<@@RXVT_NAME@@c> and B<@@RXVT_NAME@@d> use the environment
92 variable F<RXVT_SOCKET> to create a listening socket and to contact
93 the @@RXVT_NAME@@d, respectively. If the variable is missing then
94 F<<< $HOME/.rxvt-unicode-I<< <nodename> >> >>> is used.
98 Only used when the C<--opendisplay> option is specified. Must contain a
105 @@RXVT_NAME@@(7), @@RXVT_NAME@@c(1)