28
30
<h1><a name="name">NAME</a></h1>
29
<p>rxvtd - rxvt terminal daemon</p>
31
<p>urxvtd - urxvt terminal daemon</p>
33
35
<h1><a name="synopsis">SYNOPSIS</a></h1>
34
<p><strong>rxvtd</strong> [-q|--quiet] [-o|--opendisplay] [-f|--fork]</p>
36
<p><strong>urxvtd</strong> [-q|--quiet] [-o|--opendisplay] [-f|--fork]</p>
38
40
<h1><a name="description">DESCRIPTION</a></h1>
39
<p>This manpage describes the rxvtd daemon, which is the same vt102
40
terminal emulator as rxvt, but runs as a daemon that can open
41
<p>This manpage describes the urxvtd daemon, which is the same vt102
42
terminal emulator as urxvt, but runs as a daemon that can open
41
43
multiple terminal windows within the same process.</p>
42
44
<p>You can run it from your X startup scripts, for example, although it is
43
45
not dependent on a working DISPLAY and, in fact, can open windows on
44
46
multiple X displays on the same time.</p>
45
<p>Advantages of running a rxvt daemon include faster creation time
47
<p>Advantages of running a urxvt daemon include faster creation time
46
48
for terminal windows and a lot of saved memory.</p>
47
49
<p>The disadvantage is a possible impact on stability - if the
48
50
main program crashes, all processes in the terminal windows are
49
51
terminated. For example, as there is no way to cleanly react to abnormal
50
52
connection closes, <code>xkill</code> and server resets/restarts will kill the
51
<strong>rxvtd</strong> instance including all windows it has opened.</p>
53
<strong>urxvtd</strong> instance including all windows it has opened.</p>
55
57
<h1><a name="options">OPTIONS</a></h1>
56
<p><strong>rxvtd</strong> currently understands a few options only. Bundling of
58
<p><strong>urxvtd</strong> currently understands a few options only. Bundling of
57
59
options is not yet supported.</p>
59
<dt><strong><a name="item__2dq_2c__2d_2dquiet"><strong>-q</strong>, <strong>--quiet</strong></a></strong><br />
61
<dt><strong><a name="item__2dq_2c__2d_2dquiet"><strong>-q</strong>, <strong>--quiet</strong></a></strong>
62
Normally, <strong>rxvtd</strong> outputs the message <code>rxvt-unicode daemon
64
<p>Normally, <strong>urxvtd</strong> outputs the message <code>rxvt-unicode daemon
63
65
listening on <path></code> after binding to its control socket. This option
64
will suppress this message (errors and warnings will still be logged).
67
<dt><strong><a name="item__2do_2c__2d_2dopendisplay"><strong>-o</strong>, <strong>--opendisplay</strong></a></strong><br />
70
This forces <strong>rxvtd</strong> to open a connection to the current
71
<code>$DISPLAY</code> and keep it open.
74
<p>This is useful if you want to bind an instance of <strong>rxvtd</strong> to
66
will suppress this message (errors and warnings will still be logged).</p>
69
<dt><strong><a name="item__2do_2c__2d_2dopendisplay"><strong>-o</strong>, <strong>--opendisplay</strong></a></strong>
72
<p>This forces <strong>urxvtd</strong> to open a connection to the current
73
<code>$DISPLAY</code> and keep it open.</p>
76
<p>This is useful if you want to bind an instance of <strong>urxvtd</strong> to
75
77
the lifetime of a specific display/server. If the server does a reset,
76
<strong>rxvtd</strong> will be killed automatically.</p>
78
<strong>urxvtd</strong> will be killed automatically.</p>
79
<dt><strong><a name="item__2df_2c__2d_2dfork"><strong>-f</strong>, <strong>--fork</strong></a></strong><br />
81
<dt><strong><a name="item__2df_2c__2d_2dfork"><strong>-f</strong>, <strong>--fork</strong></a></strong>
82
This makes <strong>rxvtd</strong> fork after it has bound itself to its control
84
<p>This makes <strong>urxvtd</strong> fork after it has bound itself to its control
89
92
<h1><a name="examples">EXAMPLES</a></h1>
90
<p>This is a useful invocation of <strong>rxvtd</strong> in a <em>.xsession</em>-style
93
<p>This is a useful invocation of <strong>urxvtd</strong> in a <em>.xsession</em>-style
93
B<rxvtd> -q -f -o</pre>
96
B<urxvtd> -q -f -o</pre>
94
97
<p>This waits till the control socket is available, opens the current display
95
98
and forks into the background. When you log-out, the server is reset and
96
<strong>rxvtd</strong> is killed.</p>
99
<strong>urxvtd</strong> is killed.</p>
100
103
<h1><a name="environment">ENVIRONMENT</a></h1>
102
<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong><br />
105
<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong>
105
Both <strong>rxvtc</strong> and <strong>rxvtd</strong> use the environment
108
<p>Both <strong>urxvtc</strong> and <strong>urxvtd</strong> use the environment
106
109
variable <em>RXVT_SOCKET</em> to create a listening socket and to contact
107
the rxvtd, respectively. If the variable is missing,
110
the urxvtd, respectively. If the variable is missing,
108
111
<em>$HOME/.rxvt-unicode-<em><nodename</em> </em>> >>> is used. The variable must
109
specify the absolute path of the socket to create.
112
specify the absolute path of the socket to create.</p>
112
<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong><br />
115
<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong>
115
Only used when the <code>--opendisplay</code> option is specified. Must contain a
116
valid X display name.
118
<p>Only used when the <code>--opendisplay</code> option is specified. Must contain a
119
valid X display name.</p>
122
125
<h1><a name="see_also">SEE ALSO</a></h1>
123
<p>rxvt(7), <code>rxvtc(1)</code></p>
126
<p>urxvt(7), <code>urxvtc(1)</code></p>
added
removed
doc/rxvtd.1.html
