rxvt-unicode/doc/rxvtd.1.html

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
        <title>rxvtd</title>
        <meta name="description" content="Pod documentation for rxvtd" />
        <meta name="inputfile" content="&lt;standard input&gt;" />
        <meta name="outputfile" content="&lt;standard output&gt;" />
        <meta name="created" content="Mon Jun 25 00:30:33 2007" />
        <meta name="generator" content="Pod::Xhtml 1.57" />
<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head>
<body>
<div class="pod">
<!-- INDEX START -->
<h3 id="TOP">Index</h3>

<ul><li><a href="#NAME">NAME</a></li>
<li><a href="#SYNOPSIS">SYNOPSIS</a></li>
<li><a href="#DESCRIPTION">DESCRIPTION</a></li>
<li><a href="#OPTIONS">OPTIONS</a></li>
<li><a href="#EXAMPLES">EXAMPLES</a></li>
<li><a href="#ENVIRONMENT">ENVIRONMENT</a></li>
<li><a href="#SEE_ALSO">SEE ALSO</a>
</li>
</ul><hr />
<!-- INDEX END -->

<h1 id="NAME">NAME</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="NAME_CONTENT">
<p>rxvtd - rxvt terminal daemon</p>

</div>
<h1 id="SYNOPSIS">SYNOPSIS</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="SYNOPSIS_CONTENT">
<p><strong>rxvtd</strong> [-q|--quiet] [-o|--opendisplay] [-f|--fork]</p>
<p><strong>rxvtd</strong> -q -o -f    # for .xsession use</p>

</div>
<h1 id="DESCRIPTION">DESCRIPTION</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="DESCRIPTION_CONTENT">
<p>This manpage describes the rxvtd daemon, which is the same vt102
terminal emulator as rxvt, but runs as a daemon that can open
multiple terminal windows within the same process.</p>
<p>You can run it from your X startup scripts, for example, although it is
not dependent on a working DISPLAY and, in fact, can open windows on
multiple X displays on the same time.</p>
<p>Advantages of running a rxvt daemon include faster creation time
for terminal windows and a lot of saved memory.</p>
<p>The disadvantage is a possible impact on stability - if the
main program crashes, all processes in the terminal windows are
terminated. For example, as there is no way to cleanly react to abnormal
connection closes, <code>xkill</code> and server resets/restarts will kill the
<strong>rxvtd</strong> instance including all windows it has opened.</p>

</div>
<h1 id="OPTIONS">OPTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="OPTIONS_CONTENT">
<p><strong>rxvtd</strong> currently understands a few options only. Bundling of
options is not yet supported.</p>
<dl>
        <dt><strong>-q</strong>, <strong>--quiet</strong></dt>
        <dd>
                <p>Normally, <strong>rxvtd</strong> outputs the message <code>rxvt-unicode daemon
listening on &lt;path&gt;</code> after binding to its control socket. This option
will suppress this message (errors and warnings will still be logged).</p>
        </dd>
        <dt><strong>-o</strong>, <strong>--opendisplay</strong></dt>
        <dd>
                <p>This forces <strong>rxvtd</strong> to open a connection to the current
<code>$DISPLAY</code> and keep it open.</p>
                <p>This is useful if you want to bind an instance of <strong>rxvtd</strong> to
the lifetime of a specific display/server. If the server does a reset,
<strong>rxvtd</strong> will be killed automatically.</p>
        </dd>
        <dt><strong>-f</strong>, <strong>--fork</strong></dt>
        <dd>
                <p>This makes <strong>rxvtd</strong> fork after it has bound itself to its control
socket.</p>
        </dd>
</dl>

</div>
<h1 id="EXAMPLES">EXAMPLES</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="EXAMPLES_CONTENT">
<p>This is a useful invocation of <strong>rxvtd</strong> in a <cite>.xsession</cite>-style
script:</p>
<pre>   rxvtd -q -f -o

</pre>
<p>This waits till the control socket is available, opens the current display
and forks into the background. When you log-out, the server is reset and
<strong>rxvtd</strong> is killed.</p>

</div>
<h1 id="ENVIRONMENT">ENVIRONMENT</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="ENVIRONMENT_CONTENT">
<dl>
        <dt><strong>RXVT_SOCKET</strong></dt>
        <dd>
                <p>Both <strong>rxvtc</strong> and <strong>rxvtd</strong> use the environment
variable <cite>RXVT_SOCKET</cite> to create a listening socket and to contact
the rxvtd, respectively. If the variable is missing,
<cite>$HOME/.rxvt-unicode-<i>&lt;nodename&gt;</i></cite> is used. The variable must
specify the absolute path of the socket to create.</p>
        </dd>
        <dt><strong>DISPLAY</strong></dt>
        <dd>
                <p>Only used when the <code>--opendisplay</code> option is specified. Must contain a
valid X display name.</p>
        </dd>
</dl>

</div>
<h1 id="SEE_ALSO">SEE ALSO</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="SEE_ALSO_CONTENT">
<p>rxvt(7), rxvtc(1)
</p>

</div>
</div></body>
</html>
Revision:	1.8
Committed:	Sun Jun 24 22:30:52 2007 UTC (19 years, 3 months ago) by root
Content type:	text/html
Branch:	MAIN
CVS Tags:	rel-8_3
Changes since 1.7:	+1 -1 lines
Log Message:	hack around pod::xhtmls missing support for begin/end
#	User	Rev	Content
1	root	1.7	<?xml version="1.0" encoding="UTF-8"?>
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" xml:lang="en">
4	root	1.1	<head>
5	root	1.7	<title>rxvtd</title>
6			<meta name="description" content="Pod documentation for rxvtd" />
7			<meta name="inputfile" content="<standard input>" />
8			<meta name="outputfile" content="<standard output>" />
9	root	1.8	<meta name="created" content="Mon Jun 25 00:30:33 2007" />
10	root	1.7	<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>
16
17			<ul><li><a href="#NAME">NAME</a></li>
18			<li><a href="#SYNOPSIS">SYNOPSIS</a></li>
19			<li><a href="#DESCRIPTION">DESCRIPTION</a></li>
20			<li><a href="#OPTIONS">OPTIONS</a></li>
21			<li><a href="#EXAMPLES">EXAMPLES</a></li>
22			<li><a href="#ENVIRONMENT">ENVIRONMENT</a></li>
23			<li><a href="#SEE_ALSO">SEE ALSO</a>
24			</li>
25			</ul><hr />
26	root	1.1	<!-- INDEX END -->
27
28	root	1.7	<h1 id="NAME">NAME</h1><p><a href="#TOP" class="toplink">Top</a></p>
29			<div id="NAME_CONTENT">
30	root	1.5	<p>rxvtd - rxvt terminal daemon</p>
31	root	1.7
32			</div>
33			<h1 id="SYNOPSIS">SYNOPSIS</h1><p><a href="#TOP" class="toplink">Top</a></p>
34			<div id="SYNOPSIS_CONTENT">
35	root	1.5	<p><strong>rxvtd</strong> [-q\|--quiet] [-o\|--opendisplay] [-f\|--fork]</p>
36	root	1.6	<p><strong>rxvtd</strong> -q -o -f # for .xsession use</p>
37	root	1.7
38			</div>
39			<h1 id="DESCRIPTION">DESCRIPTION</h1><p><a href="#TOP" class="toplink">Top</a></p>
40			<div id="DESCRIPTION_CONTENT">
41	root	1.5	<p>This manpage describes the rxvtd daemon, which is the same vt102
42			terminal emulator as rxvt, but runs as a daemon that can open
43	root	1.1	multiple terminal windows within the same process.</p>
44			<p>You can run it from your X startup scripts, for example, although it is
45			not dependent on a working DISPLAY and, in fact, can open windows on
46			multiple X displays on the same time.</p>
47	root	1.5	<p>Advantages of running a rxvt daemon include faster creation time
48	root	1.1	for terminal windows and a lot of saved memory.</p>
49			<p>The disadvantage is a possible impact on stability - if the
50			main program crashes, all processes in the terminal windows are
51			terminated. For example, as there is no way to cleanly react to abnormal
52			connection closes, <code>xkill</code> and server resets/restarts will kill the
53	root	1.5	<strong>rxvtd</strong> instance including all windows it has opened.</p>
54	root	1.7
55			</div>
56			<h1 id="OPTIONS">OPTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
57			<div id="OPTIONS_CONTENT">
58	root	1.5	<p><strong>rxvtd</strong> currently understands a few options only. Bundling of
59	root	1.1	options is not yet supported.</p>
60			<dl>
61	root	1.7	<dt><strong>-q</strong>, <strong>--quiet</strong></dt>
62			<dd>
63			<p>Normally, <strong>rxvtd</strong> outputs the message <code>rxvt-unicode daemon
64	root	1.1	listening on <path></code> after binding to its control socket. This option
65	root	1.4	will suppress this message (errors and warnings will still be logged).</p>
66	root	1.7	</dd>
67			<dt><strong>-o</strong>, <strong>--opendisplay</strong></dt>
68			<dd>
69			<p>This forces <strong>rxvtd</strong> to open a connection to the current
70	root	1.4	<code>$DISPLAY</code> and keep it open.</p>
71	root	1.7	<p>This is useful if you want to bind an instance of <strong>rxvtd</strong> to
72	root	1.1	the lifetime of a specific display/server. If the server does a reset,
73	root	1.5	<strong>rxvtd</strong> will be killed automatically.</p>
74	root	1.7	</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
78	root	1.4	socket.</p>
79	root	1.7	</dd>
80	root	1.4	</dl>
81	root	1.7
82			</div>
83			<h1 id="EXAMPLES">EXAMPLES</h1><p><a href="#TOP" class="toplink">Top</a></p>
84			<div id="EXAMPLES_CONTENT">
85			<p>This is a useful invocation of <strong>rxvtd</strong> in a <cite>.xsession</cite>-style
86	root	1.1	script:</p>
87	root	1.7	<pre> rxvtd -q -f -o
88
89			</pre>
90	root	1.1	<p>This waits till the control socket is available, opens the current display
91			and forks into the background. When you log-out, the server is reset and
92	root	1.5	<strong>rxvtd</strong> is killed.</p>
93	root	1.7
94			</div>
95			<h1 id="ENVIRONMENT">ENVIRONMENT</h1><p><a href="#TOP" class="toplink">Top</a></p>
96			<div id="ENVIRONMENT_CONTENT">
97	root	1.1	<dl>
98	root	1.7	<dt><strong>RXVT_SOCKET</strong></dt>
99			<dd>
100			<p>Both <strong>rxvtc</strong> and <strong>rxvtd</strong> use the environment
101			variable <cite>RXVT_SOCKET</cite> to create a listening socket and to contact
102	root	1.5	the rxvtd, respectively. If the variable is missing,
103	root	1.7	<cite>$HOME/.rxvt-unicode-<i><nodename></i></cite> is used. The variable must
104	root	1.4	specify the absolute path of the socket to create.</p>
105	root	1.7	</dd>
106			<dt><strong>DISPLAY</strong></dt>
107			<dd>
108			<p>Only used when the <code>--opendisplay</code> option is specified. Must contain a
109	root	1.4	valid X display name.</p>
110	root	1.7	</dd>
111	root	1.1	</dl>
112	root	1.7
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)
117	root	1.1	</p>
118
119	root	1.7	</div>
120			</div></body>
121	root	1.1	</html>