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.3 by root, Sat Dec 17 20:55:45 2005 UTC vs.
Revision 1.9 by root, Sat Oct 27 12:09:02 2007 UTC

1<?xml version="1.0" encoding="UTF-8"?>
1<!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">
2<html xmlns="http://www.w3.org/1999/xhtml"> 3<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
3<head> 4<head>
4<title>rxvtd - rxvt terminal daemon</title> 5 <title>urxvtd</title>
5<link rev="made" href="mailto:perl-binary@plan9.de" /> 6 <meta name="description" content="Pod documentation for urxvtd" />
6</head> 7 <meta name="inputfile" content="&lt;standard input&gt;" />
8 <meta name="outputfile" content="&lt;standard output&gt;" />
9 <meta name="created" content="Sat Oct 27 14:07:34 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>
7 16
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> 17<ul><li><a href="#NAME">NAME</a></li>
16 <li><a href="#synopsis">SYNOPSIS</a></li> 18<li><a href="#SYNOPSIS">SYNOPSIS</a></li>
17 <li><a href="#description">DESCRIPTION</a></li> 19<li><a href="#DESCRIPTION">DESCRIPTION</a></li>
18 <li><a href="#options">OPTIONS</a></li> 20<li><a href="#OPTIONS">OPTIONS</a></li>
19 <li><a href="#examples">EXAMPLES</a></li> 21<li><a href="#EXAMPLES">EXAMPLES</a></li>
20 <li><a href="#environment">ENVIRONMENT</a></li> 22<li><a href="#ENVIRONMENT">ENVIRONMENT</a></li>
21 <li><a href="#see_also">SEE ALSO</a></li> 23<li><a href="#SEE_ALSO">SEE ALSO</a>
22</ul> 24</li>
25</ul><hr />
23<!-- INDEX END --> 26<!-- INDEX END -->
24 27
25<hr /> 28<h1 id="NAME">NAME</h1><p><a href="#TOP" class="toplink">Top</a></p>
26<p> 29<div id="NAME_CONTENT">
27</p>
28<h1><a name="name">NAME</a></h1>
29<p>rxvtd - rxvt terminal daemon</p> 30<p>urxvtd - urxvt terminal daemon</p>
30<p> 31
31</p> 32</div>
32<hr /> 33<h1 id="SYNOPSIS">SYNOPSIS</h1><p><a href="#TOP" class="toplink">Top</a></p>
33<h1><a name="synopsis">SYNOPSIS</a></h1> 34<div id="SYNOPSIS_CONTENT">
34<p><strong>rxvtd</strong> [-q|--quiet] [-o|--opendisplay] [-f|--fork]</p> 35<p><strong>urxvtd</strong> [-q|--quiet] [-o|--opendisplay] [-f|--fork]</p>
35<p> 36<p><strong>urxvtd</strong> -q -o -f # for .xsession use</p>
36</p> 37
37<hr /> 38</div>
38<h1><a name="description">DESCRIPTION</a></h1> 39<h1 id="DESCRIPTION">DESCRIPTION</h1><p><a href="#TOP" class="toplink">Top</a></p>
40<div id="DESCRIPTION_CONTENT">
39<p>This manpage describes the rxvtd daemon, which is the same vt102 41<p>This manpage describes the urxvtd daemon, which is the same vt102
40terminal emulator as rxvt, but runs as a daemon that can open 42terminal emulator as urxvt, but runs as a daemon that can open
41multiple terminal windows within the same process.</p> 43multiple terminal windows within the same process.</p>
42<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
43not 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
44multiple X displays on the same time.</p> 46multiple 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
46for terminal windows and a lot of saved memory.</p> 48for terminal windows and a lot of saved memory.</p>
47<p>The disadvantage is a possible impact on stability - if the 49<p>The disadvantage is a possible impact on stability - if the
48main program crashes, all processes in the terminal windows are 50main program crashes, all processes in the terminal windows are
49terminated. 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
50connection closes, <code>xkill</code> and server resets/restarts will kill the 52connection 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>
52<p> 54
53</p> 55</div>
54<hr /> 56<h1 id="OPTIONS">OPTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
55<h1><a name="options">OPTIONS</a></h1> 57<div id="OPTIONS_CONTENT">
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
57options is not yet supported.</p> 59options is not yet supported.</p>
58<dl> 60<dl>
59<dt><strong><a name="item__2dq_2c__2d_2dquiet"><strong>-q</strong>, <strong>--quiet</strong></a></strong><br /> 61 <dt><strong>-q</strong>, <strong>--quiet</strong></dt>
60</dt>
61<dd> 62 <dd>
62Normally, <strong>rxvtd</strong> outputs the message <code>rxvt-unicode daemon 63 <p>Normally, <strong>urxvtd</strong> outputs the message <code>rxvt-unicode daemon
63listening 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
64will suppress this message (errors and warnings will still be logged). 65will suppress this message (errors and warnings will still be logged).</p>
65</dd> 66 </dd>
66<p></p> 67 <dt><strong>-o</strong>, <strong>--opendisplay</strong></dt>
67<dt><strong><a name="item__2do_2c__2d_2dopendisplay"><strong>-o</strong>, <strong>--opendisplay</strong></a></strong><br />
68</dt>
69<dd> 68 <dd>
70This forces <strong>rxvtd</strong> to open a connection to the current 69 <p>This forces <strong>urxvtd</strong> to open a connection to the current
71<code>$DISPLAY</code> and keep it open. 70<code>$DISPLAY</code> and keep it open.</p>
72</dd>
73<dd>
74<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>urxvtd</strong> to
75the 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,
76<strong>rxvtd</strong> will be killed automatically.</p> 73<strong>urxvtd</strong> will be killed automatically.</p>
77</dd> 74 </dd>
78<p></p> 75 <dt><strong>-f</strong>, <strong>--fork</strong></dt>
79<dt><strong><a name="item__2df_2c__2d_2dfork"><strong>-f</strong>, <strong>--fork</strong></a></strong><br />
80</dt>
81<dd> 76 <dd>
82This makes <strong>rxvtd</strong> fork after it has bound itself to its control 77 <p>This makes <strong>urxvtd</strong> fork after it has bound itself to its control
83socket. 78socket.</p>
84</dd> 79 </dd>
85<p></p></dl> 80</dl>
86<p> 81
87</p> 82</div>
88<hr /> 83<h1 id="EXAMPLES">EXAMPLES</h1><p><a href="#TOP" class="toplink">Top</a></p>
89<h1><a name="examples">EXAMPLES</a></h1> 84<div id="EXAMPLES_CONTENT">
90<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>urxvtd</strong> in a <cite>.xsession</cite>-style
91script:</p> 86script:</p>
87<pre> urxvtd -q -f -o
88
92<pre> 89</pre>
93 B&lt;rxvtd&gt; -q -f -o</pre>
94<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
95and 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
96<strong>rxvtd</strong> is killed.</p> 92<strong>urxvtd</strong> is killed.</p>
97<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>urxvtc</strong> and <strong>urxvtd</strong> use the environment
101variable <cite>RXVT_SOCKET</cite> to create a listening socket and to contact
102the urxvtd, 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>urxvt(7), urxvtc(1)
98</p> 117</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>
105Both <strong>rxvtc</strong> and <strong>rxvtd</strong> use the environment
106variable <em>RXVT_SOCKET</em> to create a listening socket and to contact
107the rxvtd, respectively. If the variable is missing,
108<em>$HOME/.rxvt-unicode-<em>&lt;nodename</em> </em>&gt; &gt;&gt;&gt; is used. The variable must
109specify the absolute path of the socket to create.
110</dd>
111<p></p>
112<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong><br />
113</dt>
114<dd>
115Only used when the <code>--opendisplay</code> option is specified. Must contain a
116valid X display name.
117</dd>
118</dl>
119<p>
120</p>
121<hr />
122<h1><a name="see_also">SEE ALSO</a></h1>
123<p>rxvt(7), <code>rxvtc(1)</code></p>
124 118
125</body> 119</div>
126 120</div></body>
127</html> 121</html>

Diff Legend

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