ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvtd.1.html
(Generate patch)

Comparing rxvt-unicode/doc/rxvtd.1.html (file contents):
Revision 1.6 by root, Sat Jun 2 05:13:42 2007 UTC vs.
Revision 1.7 by root, Sun Jun 24 22:12:18 2007 UTC

1<?xml version="1.0" ?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> 2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml"> 3<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
4<head> 4<head>
5<title>rxvtd - rxvt terminal daemon</title> 5 <title>rxvtd</title>
6<meta http-equiv="content-type" content="text/html; charset=utf-8" /> 6 <meta name="description" content="Pod documentation for rxvtd" />
7<link rev="made" href="mailto:perl-binary@plan9.de" /> 7 <meta name="inputfile" content="&lt;standard input&gt;" />
8</head> 8 <meta name="outputfile" content="&lt;standard output&gt;" />
9 <meta name="created" content="Mon Jun 25 00:11:17 2007" />
10 <meta name="generator" content="Pod::Xhtml 1.57" />
11<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head>
12<body>
13<div class="pod">
14<!-- INDEX START -->
15<h3 id="TOP">Index</h3>
9 16
10<body style="background-color: white">
11
12<p><a name="__index__"></a></p>
13<!-- INDEX BEGIN -->
14
15<ul>
16
17 <li><a href="#name">NAME</a></li> 17<ul><li><a href="#NAME">NAME</a></li>
18 <li><a href="#synopsis">SYNOPSIS</a></li> 18<li><a href="#SYNOPSIS">SYNOPSIS</a></li>
19 <li><a href="#description">DESCRIPTION</a></li> 19<li><a href="#DESCRIPTION">DESCRIPTION</a></li>
20 <li><a href="#options">OPTIONS</a></li> 20<li><a href="#OPTIONS">OPTIONS</a></li>
21 <li><a href="#examples">EXAMPLES</a></li> 21<li><a href="#EXAMPLES">EXAMPLES</a></li>
22 <li><a href="#environment">ENVIRONMENT</a></li> 22<li><a href="#ENVIRONMENT">ENVIRONMENT</a></li>
23 <li><a href="#see_also">SEE ALSO</a></li> 23<li><a href="#SEE_ALSO">SEE ALSO</a>
24</ul> 24</li>
25</ul><hr />
25<!-- INDEX END --> 26<!-- INDEX END -->
26 27
27<hr /> 28<h1 id="NAME">NAME</h1><p><a href="#TOP" class="toplink">Top</a></p>
28<p> 29<div id="NAME_CONTENT">
29</p>
30<h1><a name="name">NAME</a></h1>
31<p>rxvtd - rxvt terminal daemon</p> 30<p>rxvtd - rxvt terminal daemon</p>
32<p> 31
33</p> 32</div>
34<hr /> 33<h1 id="SYNOPSIS">SYNOPSIS</h1><p><a href="#TOP" class="toplink">Top</a></p>
35<h1><a name="synopsis">SYNOPSIS</a></h1> 34<div id="SYNOPSIS_CONTENT">
36<p><strong>rxvtd</strong> [-q|--quiet] [-o|--opendisplay] [-f|--fork]</p> 35<p><strong>rxvtd</strong> [-q|--quiet] [-o|--opendisplay] [-f|--fork]</p>
37<p><strong>rxvtd</strong> -q -o -f # for .xsession use</p> 36<p><strong>rxvtd</strong> -q -o -f # for .xsession use</p>
38<p> 37
39</p> 38</div>
40<hr /> 39<h1 id="DESCRIPTION">DESCRIPTION</h1><p><a href="#TOP" class="toplink">Top</a></p>
41<h1><a name="description">DESCRIPTION</a></h1> 40<div id="DESCRIPTION_CONTENT">
42<p>This manpage describes the rxvtd daemon, which is the same vt102 41<p>This manpage describes the rxvtd daemon, which is the same vt102
43terminal emulator as rxvt, but runs as a daemon that can open 42terminal emulator as rxvt, but runs as a daemon that can open
44multiple terminal windows within the same process.</p> 43multiple terminal windows within the same process.</p>
45<p>You can run it from your X startup scripts, for example, although it is 44<p>You can run it from your X startup scripts, for example, although it is
46not dependent on a working DISPLAY and, in fact, can open windows on 45not dependent on a working DISPLAY and, in fact, can open windows on
… …
50<p>The disadvantage is a possible impact on stability - if the 49<p>The disadvantage is a possible impact on stability - if the
51main program crashes, all processes in the terminal windows are 50main program crashes, all processes in the terminal windows are
52terminated. For example, as there is no way to cleanly react to abnormal 51terminated. For example, as there is no way to cleanly react to abnormal
53connection closes, <code>xkill</code> and server resets/restarts will kill the 52connection closes, <code>xkill</code> and server resets/restarts will kill the
54<strong>rxvtd</strong> instance including all windows it has opened.</p> 53<strong>rxvtd</strong> instance including all windows it has opened.</p>
55<p> 54
56</p> 55</div>
57<hr /> 56<h1 id="OPTIONS">OPTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
58<h1><a name="options">OPTIONS</a></h1> 57<div id="OPTIONS_CONTENT">
59<p><strong>rxvtd</strong> currently understands a few options only. Bundling of 58<p><strong>rxvtd</strong> currently understands a few options only. Bundling of
60options is not yet supported.</p> 59options is not yet supported.</p>
61<dl> 60<dl>
62<dt><strong><a name="item__2dq_2c__2d_2dquiet"><strong>-q</strong>, <strong>--quiet</strong></a></strong> 61 <dt><strong>-q</strong>, <strong>--quiet</strong></dt>
63
64<dd> 62 <dd>
65<p>Normally, <strong>rxvtd</strong> outputs the message <code>rxvt-unicode daemon 63 <p>Normally, <strong>rxvtd</strong> outputs the message <code>rxvt-unicode daemon
66listening on &lt;path&gt;</code> after binding to its control socket. This option 64listening on &lt;path&gt;</code> after binding to its control socket. This option
67will suppress this message (errors and warnings will still be logged).</p> 65will suppress this message (errors and warnings will still be logged).</p>
68</dd> 66 </dd>
69</li> 67 <dt><strong>-o</strong>, <strong>--opendisplay</strong></dt>
70<dt><strong><a name="item__2do_2c__2d_2dopendisplay"><strong>-o</strong>, <strong>--opendisplay</strong></a></strong>
71
72<dd> 68 <dd>
73<p>This forces <strong>rxvtd</strong> to open a connection to the current 69 <p>This forces <strong>rxvtd</strong> to open a connection to the current
74<code>$DISPLAY</code> and keep it open.</p> 70<code>$DISPLAY</code> and keep it open.</p>
75</dd>
76<dd>
77<p>This is useful if you want to bind an instance of <strong>rxvtd</strong> to 71 <p>This is useful if you want to bind an instance of <strong>rxvtd</strong> to
78the lifetime of a specific display/server. If the server does a reset, 72the lifetime of a specific display/server. If the server does a reset,
79<strong>rxvtd</strong> will be killed automatically.</p> 73<strong>rxvtd</strong> will be killed automatically.</p>
80</dd> 74 </dd>
75 <dt><strong>-f</strong>, <strong>--fork</strong></dt>
76 <dd>
77 <p>This makes <strong>rxvtd</strong> fork after it has bound itself to its control
78socket.</p>
79 </dd>
81</li> 80</dl>
82<dt><strong><a name="item__2df_2c__2d_2dfork"><strong>-f</strong>, <strong>--fork</strong></a></strong>
83 81
84<dd> 82</div>
85<p>This makes <strong>rxvtd</strong> fork after it has bound itself to its control 83<h1 id="EXAMPLES">EXAMPLES</h1><p><a href="#TOP" class="toplink">Top</a></p>
86socket.</p> 84<div id="EXAMPLES_CONTENT">
87</dd>
88</li>
89</dl>
90<p>
91</p>
92<hr />
93<h1><a name="examples">EXAMPLES</a></h1>
94<p>This is a useful invocation of <strong>rxvtd</strong> in a <em>.xsession</em>-style 85<p>This is a useful invocation of <strong>rxvtd</strong> in a <cite>.xsession</cite>-style
95script:</p> 86script:</p>
87<pre> rxvtd -q -f -o
88
96<pre> 89</pre>
97 rxvtd -q -f -o</pre>
98<p>This waits till the control socket is available, opens the current display 90<p>This waits till the control socket is available, opens the current display
99and forks into the background. When you log-out, the server is reset and 91and forks into the background. When you log-out, the server is reset and
100<strong>rxvtd</strong> is killed.</p> 92<strong>rxvtd</strong> is killed.</p>
101<p> 93
94</div>
95<h1 id="ENVIRONMENT">ENVIRONMENT</h1><p><a href="#TOP" class="toplink">Top</a></p>
96<div id="ENVIRONMENT_CONTENT">
97<dl>
98 <dt><strong>RXVT_SOCKET</strong></dt>
99 <dd>
100 <p>Both <strong>rxvtc</strong> and <strong>rxvtd</strong> use the environment
101variable <cite>RXVT_SOCKET</cite> to create a listening socket and to contact
102the rxvtd, respectively. If the variable is missing,
103<cite>$HOME/.rxvt-unicode-<i>&lt;nodename&gt;</i></cite> is used. The variable must
104specify the absolute path of the socket to create.</p>
105 </dd>
106 <dt><strong>DISPLAY</strong></dt>
107 <dd>
108 <p>Only used when the <code>--opendisplay</code> option is specified. Must contain a
109valid X display name.</p>
110 </dd>
111</dl>
112
113</div>
114<h1 id="SEE_ALSO">SEE ALSO</h1><p><a href="#TOP" class="toplink">Top</a></p>
115<div id="SEE_ALSO_CONTENT">
116<p>rxvt(7), rxvtc(1)
102</p> 117</p>
103<hr />
104<h1><a name="environment">ENVIRONMENT</a></h1>
105<dl>
106<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong>
107 118
108<dd> 119</div>
109<p>Both <strong>rxvtc</strong> and <strong>rxvtd</strong> use the environment 120</div></body>
110variable <em>RXVT_SOCKET</em> to create a listening socket and to contact
111the rxvtd, respectively. If the variable is missing,
112<em>$HOME/.rxvt-unicode-<em>&lt;nodename</em> </em>&gt; &gt;&gt;&gt; is used. The variable must
113specify the absolute path of the socket to create.</p>
114</dd>
115</li>
116<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong>
117
118<dd>
119<p>Only used when the <code>--opendisplay</code> option is specified. Must contain a
120valid X display name.</p>
121</dd>
122</li>
123</dl>
124<p>
125</p>
126<hr />
127<h1><a name="see_also">SEE ALSO</a></h1>
128<p>rxvt(7), <code>rxvtc(1)</code></p>
129
130</body>
131
132</html> 121</html>

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines