1 |
root |
1.1 |
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> |
2 |
|
|
<html xmlns="http://www.w3.org/1999/xhtml"> |
3 |
|
|
<head> |
4 |
|
|
<title>rxvtd - rxvt terminal daemon</title> |
5 |
|
|
<link rev="made" href="mailto:perl-binary@plan9.de" /> |
6 |
|
|
</head> |
7 |
|
|
|
8 |
|
|
<body style="background-color: white"> |
9 |
|
|
|
10 |
|
|
<p><a name="__index__"></a></p> |
11 |
|
|
<!-- INDEX BEGIN --> |
12 |
|
|
|
13 |
|
|
<ul> |
14 |
|
|
|
15 |
|
|
<li><a href="#name">NAME</a></li> |
16 |
|
|
<li><a href="#synopsis">SYNOPSIS</a></li> |
17 |
|
|
<li><a href="#description">DESCRIPTION</a></li> |
18 |
|
|
<li><a href="#options">OPTIONS</a></li> |
19 |
|
|
<li><a href="#examples">EXAMPLES</a></li> |
20 |
|
|
<li><a href="#environment">ENVIRONMENT</a></li> |
21 |
|
|
<li><a href="#see_also">SEE ALSO</a></li> |
22 |
|
|
</ul> |
23 |
|
|
<!-- INDEX END --> |
24 |
|
|
|
25 |
|
|
<hr /> |
26 |
|
|
<p> |
27 |
|
|
</p> |
28 |
|
|
<h1><a name="name">NAME</a></h1> |
29 |
|
|
<p>rxvtd - rxvt terminal daemon</p> |
30 |
|
|
<p> |
31 |
|
|
</p> |
32 |
|
|
<hr /> |
33 |
|
|
<h1><a name="synopsis">SYNOPSIS</a></h1> |
34 |
|
|
<p><strong>rxvtd</strong> [-q|--quiet] [-o|--opendisplay] [-f|--fork]</p> |
35 |
|
|
<p> |
36 |
|
|
</p> |
37 |
|
|
<hr /> |
38 |
|
|
<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 |
|
|
multiple terminal windows within the same process.</p> |
42 |
|
|
<p>You can run it from your X startup scripts, for example, although it is |
43 |
|
|
not dependent on a working DISPLAY and, in fact, can open windows on |
44 |
|
|
multiple X displays on the same time.</p> |
45 |
|
|
<p>Advantages of running a rxvt daemon include faster creation time |
46 |
|
|
for terminal windows and a lot of saved memory.</p> |
47 |
|
|
<p>The disadvantage is a possible impact on stability - if the |
48 |
|
|
main program crashes, all processes in the terminal windows are |
49 |
|
|
terminated. For example, as there is no way to cleanly react to abnormal |
50 |
|
|
connection closes, <code>xkill</code> and server resets/restarts will kill the |
51 |
|
|
<strong>rxvtd</strong> instance including all windows it has opened.</p> |
52 |
|
|
<p> |
53 |
|
|
</p> |
54 |
|
|
<hr /> |
55 |
|
|
<h1><a name="options">OPTIONS</a></h1> |
56 |
|
|
<p><strong>rxvtd</strong> currently understands a few options only. Bundling of |
57 |
|
|
options is not yet supported.</p> |
58 |
|
|
<dl> |
59 |
|
|
<dt><strong><a name="item__2dq_2c__2d_2dquiet"><strong>-q</strong>, <strong>--quiet</strong></a></strong><br /> |
60 |
|
|
</dt> |
61 |
|
|
<dd> |
62 |
|
|
Normally, <strong>rxvtd</strong> outputs the message <code>rxvt-unicode daemon |
63 |
|
|
listening on <path></code> after binding to its control socket. This option |
64 |
root |
1.2 |
will suppress this message (errors and warnings will still be logged). |
65 |
root |
1.1 |
</dd> |
66 |
|
|
<p></p> |
67 |
|
|
<dt><strong><a name="item__2do_2c__2d_2dopendisplay"><strong>-o</strong>, <strong>--opendisplay</strong></a></strong><br /> |
68 |
|
|
</dt> |
69 |
|
|
<dd> |
70 |
|
|
This forces <strong>rxvtd</strong> to open a connection to the current |
71 |
|
|
<code>$DISPLAY</code> and keep it open. |
72 |
|
|
</dd> |
73 |
|
|
<dd> |
74 |
|
|
<p>This is useful if you want to bind an instance of <strong>rxvtd</strong> to |
75 |
|
|
the lifetime of a specific display/server. If the server does a reset, |
76 |
|
|
<strong>rxvtd</strong> will be killed automatically.</p> |
77 |
|
|
</dd> |
78 |
|
|
<p></p> |
79 |
|
|
<dt><strong><a name="item__2df_2c__2d_2dfork"><strong>-f</strong>, <strong>--fork</strong></a></strong><br /> |
80 |
|
|
</dt> |
81 |
|
|
<dd> |
82 |
|
|
This makes <strong>rxvtd</strong> fork after it has bound itself to its control |
83 |
|
|
socket. |
84 |
|
|
</dd> |
85 |
|
|
<p></p></dl> |
86 |
|
|
<p> |
87 |
|
|
</p> |
88 |
|
|
<hr /> |
89 |
|
|
<h1><a name="examples">EXAMPLES</a></h1> |
90 |
|
|
<p>This is a useful invocation of <strong>rxvtd</strong> in a <em>.xsession</em>-style |
91 |
|
|
script:</p> |
92 |
|
|
<pre> |
93 |
|
|
B<rxvtd> -q -f -o</pre> |
94 |
|
|
<p>This waits till the control socket is available, opens the current display |
95 |
|
|
and forks into the background. When you log-out, the server is reset and |
96 |
|
|
<strong>rxvtd</strong> is killed.</p> |
97 |
|
|
<p> |
98 |
|
|
</p> |
99 |
|
|
<hr /> |
100 |
|
|
<h1><a name="environment">ENVIRONMENT</a></h1> |
101 |
|
|
<dl> |
102 |
|
|
<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong><br /> |
103 |
|
|
</dt> |
104 |
|
|
<dd> |
105 |
|
|
Both <strong>rxvtc</strong> and <strong>rxvtd</strong> use the environment variable |
106 |
|
|
<em>RXVT_SOCKET</em> to create a listening socket and to contact |
107 |
|
|
the rxvtd, respectively. If the variable is missing, |
108 |
|
|
<em>$HOME/.rxvt-unicode-<em><nodename</em> </em>> >>> is used. |
109 |
|
|
</dd> |
110 |
|
|
<p></p> |
111 |
|
|
<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong><br /> |
112 |
|
|
</dt> |
113 |
|
|
<dd> |
114 |
|
|
Only used when the <code>--opendisplay</code> option is specified. Must contain a |
115 |
|
|
valid X display name. |
116 |
|
|
</dd> |
117 |
|
|
</dl> |
118 |
|
|
<p> |
119 |
|
|
</p> |
120 |
|
|
<hr /> |
121 |
|
|
<h1><a name="see_also">SEE ALSO</a></h1> |
122 |
|
|
<p>rxvt(7), <code>rxvtc(1)</code></p> |
123 |
|
|
|
124 |
|
|
</body> |
125 |
|
|
|
126 |
|
|
</html> |