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.4 by root, Mon Jul 17 19:20:29 2006 UTC vs.
Revision 1.5 by root, Thu Nov 2 17:37:47 2006 UTC

1<?xml version="1.0" ?> 1<?xml version="1.0" ?>
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.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml"> 3<html xmlns="http://www.w3.org/1999/xhtml">
4<head> 4<head>
5<title>urxvtd - urxvt terminal daemon</title> 5<title>rxvtd - rxvt terminal daemon</title>
6<meta http-equiv="content-type" content="text/html; charset=utf-8" /> 6<meta http-equiv="content-type" content="text/html; charset=utf-8" />
7<link rev="made" href="mailto:perl-binary@plan9.de" /> 7<link rev="made" href="mailto:perl-binary@plan9.de" />
8</head> 8</head>
9 9
10<body style="background-color: white"> 10<body style="background-color: white">
… …
26 26
27<hr /> 27<hr />
28<p> 28<p>
29</p> 29</p>
30<h1><a name="name">NAME</a></h1> 30<h1><a name="name">NAME</a></h1>
31<p>urxvtd - urxvt terminal daemon</p> 31<p>rxvtd - rxvt terminal daemon</p>
32<p> 32<p>
33</p> 33</p>
34<hr /> 34<hr />
35<h1><a name="synopsis">SYNOPSIS</a></h1> 35<h1><a name="synopsis">SYNOPSIS</a></h1>
36<p><strong>urxvtd</strong> [-q|--quiet] [-o|--opendisplay] [-f|--fork]</p> 36<p><strong>rxvtd</strong> [-q|--quiet] [-o|--opendisplay] [-f|--fork]</p>
37<p> 37<p>
38</p> 38</p>
39<hr /> 39<hr />
40<h1><a name="description">DESCRIPTION</a></h1> 40<h1><a name="description">DESCRIPTION</a></h1>
41<p>This manpage describes the urxvtd daemon, which is the same vt102 41<p>This manpage describes the rxvtd daemon, which is the same vt102
42terminal emulator as urxvt, but runs as a daemon that can open 42terminal emulator as rxvt, but runs as a daemon that can open
43multiple terminal windows within the same process.</p> 43multiple terminal windows within the same process.</p>
44<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
45not 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
46multiple X displays on the same time.</p> 46multiple X displays on the same time.</p>
47<p>Advantages of running a urxvt daemon include faster creation time 47<p>Advantages of running a rxvt daemon include faster creation time
48for terminal windows and a lot of saved memory.</p> 48for terminal windows and a lot of saved memory.</p>
49<p>The disadvantage is a possible impact on stability - if the 49<p>The disadvantage is a possible impact on stability - if the
50main program crashes, all processes in the terminal windows are 50main program crashes, all processes in the terminal windows are
51terminated. 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
52connection closes, <code>xkill</code> and server resets/restarts will kill the 52connection closes, <code>xkill</code> and server resets/restarts will kill the
53<strong>urxvtd</strong> instance including all windows it has opened.</p> 53<strong>rxvtd</strong> instance including all windows it has opened.</p>
54<p> 54<p>
55</p> 55</p>
56<hr /> 56<hr />
57<h1><a name="options">OPTIONS</a></h1> 57<h1><a name="options">OPTIONS</a></h1>
58<p><strong>urxvtd</strong> currently understands a few options only. Bundling of 58<p><strong>rxvtd</strong> currently understands a few options only. Bundling of
59options is not yet supported.</p> 59options is not yet supported.</p>
60<dl> 60<dl>
61<dt><strong><a name="item__2dq_2c__2d_2dquiet"><strong>-q</strong>, <strong>--quiet</strong></a></strong> 61<dt><strong><a name="item__2dq_2c__2d_2dquiet"><strong>-q</strong>, <strong>--quiet</strong></a></strong>
62 62
63<dd> 63<dd>
64<p>Normally, <strong>urxvtd</strong> outputs the message <code>rxvt-unicode daemon 64<p>Normally, <strong>rxvtd</strong> outputs the message <code>rxvt-unicode daemon
65listening on &lt;path&gt;</code> after binding to its control socket. This option 65listening on &lt;path&gt;</code> after binding to its control socket. This option
66will suppress this message (errors and warnings will still be logged).</p> 66will suppress this message (errors and warnings will still be logged).</p>
67</dd> 67</dd>
68</li> 68</li>
69<dt><strong><a name="item__2do_2c__2d_2dopendisplay"><strong>-o</strong>, <strong>--opendisplay</strong></a></strong> 69<dt><strong><a name="item__2do_2c__2d_2dopendisplay"><strong>-o</strong>, <strong>--opendisplay</strong></a></strong>
70 70
71<dd> 71<dd>
72<p>This forces <strong>urxvtd</strong> to open a connection to the current 72<p>This forces <strong>rxvtd</strong> to open a connection to the current
73<code>$DISPLAY</code> and keep it open.</p> 73<code>$DISPLAY</code> and keep it open.</p>
74</dd> 74</dd>
75<dd> 75<dd>
76<p>This is useful if you want to bind an instance of <strong>urxvtd</strong> to 76<p>This is useful if you want to bind an instance of <strong>rxvtd</strong> to
77the lifetime of a specific display/server. If the server does a reset, 77the lifetime of a specific display/server. If the server does a reset,
78<strong>urxvtd</strong> will be killed automatically.</p> 78<strong>rxvtd</strong> will be killed automatically.</p>
79</dd> 79</dd>
80</li> 80</li>
81<dt><strong><a name="item__2df_2c__2d_2dfork"><strong>-f</strong>, <strong>--fork</strong></a></strong> 81<dt><strong><a name="item__2df_2c__2d_2dfork"><strong>-f</strong>, <strong>--fork</strong></a></strong>
82 82
83<dd> 83<dd>
84<p>This makes <strong>urxvtd</strong> fork after it has bound itself to its control 84<p>This makes <strong>rxvtd</strong> fork after it has bound itself to its control
85socket.</p> 85socket.</p>
86</dd> 86</dd>
87</li> 87</li>
88</dl> 88</dl>
89<p> 89<p>
90</p> 90</p>
91<hr /> 91<hr />
92<h1><a name="examples">EXAMPLES</a></h1> 92<h1><a name="examples">EXAMPLES</a></h1>
93<p>This is a useful invocation of <strong>urxvtd</strong> in a <em>.xsession</em>-style 93<p>This is a useful invocation of <strong>rxvtd</strong> in a <em>.xsession</em>-style
94script:</p> 94script:</p>
95<pre> 95<pre>
96 B&lt;urxvtd&gt; -q -f -o</pre> 96 rxvtd -q -f -o</pre>
97<p>This waits till the control socket is available, opens the current display 97<p>This waits till the control socket is available, opens the current display
98and forks into the background. When you log-out, the server is reset and 98and forks into the background. When you log-out, the server is reset and
99<strong>urxvtd</strong> is killed.</p> 99<strong>rxvtd</strong> is killed.</p>
100<p> 100<p>
101</p> 101</p>
102<hr /> 102<hr />
103<h1><a name="environment">ENVIRONMENT</a></h1> 103<h1><a name="environment">ENVIRONMENT</a></h1>
104<dl> 104<dl>
105<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong> 105<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong>
106 106
107<dd> 107<dd>
108<p>Both <strong>urxvtc</strong> and <strong>urxvtd</strong> use the environment 108<p>Both <strong>rxvtc</strong> and <strong>rxvtd</strong> use the environment
109variable <em>RXVT_SOCKET</em> to create a listening socket and to contact 109variable <em>RXVT_SOCKET</em> to create a listening socket and to contact
110the urxvtd, respectively. If the variable is missing, 110the rxvtd, respectively. If the variable is missing,
111<em>$HOME/.rxvt-unicode-<em>&lt;nodename</em> </em>&gt; &gt;&gt;&gt; is used. The variable must 111<em>$HOME/.rxvt-unicode-<em>&lt;nodename</em> </em>&gt; &gt;&gt;&gt; is used. The variable must
112specify the absolute path of the socket to create.</p> 112specify the absolute path of the socket to create.</p>
113</dd> 113</dd>
114</li> 114</li>
115<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong> 115<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong>
… …
121</dl> 121</dl>
122<p> 122<p>
123</p> 123</p>
124<hr /> 124<hr />
125<h1><a name="see_also">SEE ALSO</a></h1> 125<h1><a name="see_also">SEE ALSO</a></h1>
126<p>urxvt(7), <code>urxvtc(1)</code></p> 126<p>rxvt(7), <code>rxvtc(1)</code></p>
127 127
128</body> 128</body>
129 129
130</html> 130</html>

Diff Legend

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