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"> |
3 |
<html xmlns="http://www.w3.org/1999/xhtml"> |
4 |
<head> |
5 |
<title>urxvtd - urxvt terminal daemon</title> |
6 |
<meta http-equiv="content-type" content="text/html; charset=utf-8" /> |
7 |
<link rev="made" href="mailto:perl-binary@plan9.de" /> |
8 |
</head> |
9 |
|
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> |
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></li> |
24 |
</ul> |
25 |
<!-- INDEX END --> |
26 |
|
27 |
<hr /> |
28 |
<p> |
29 |
</p> |
30 |
<h1><a name="name">NAME</a></h1> |
31 |
<p>urxvtd - urxvt terminal daemon</p> |
32 |
<p> |
33 |
</p> |
34 |
<hr /> |
35 |
<h1><a name="synopsis">SYNOPSIS</a></h1> |
36 |
<p><strong>urxvtd</strong> [-q|--quiet] [-o|--opendisplay] [-f|--fork]</p> |
37 |
<p> |
38 |
</p> |
39 |
<hr /> |
40 |
<h1><a name="description">DESCRIPTION</a></h1> |
41 |
<p>This manpage describes the urxvtd daemon, which is the same vt102 |
42 |
terminal emulator as urxvt, but runs as a daemon that can open |
43 |
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 |
<p>Advantages of running a urxvt daemon include faster creation time |
48 |
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 |
<strong>urxvtd</strong> instance including all windows it has opened.</p> |
54 |
<p> |
55 |
</p> |
56 |
<hr /> |
57 |
<h1><a name="options">OPTIONS</a></h1> |
58 |
<p><strong>urxvtd</strong> currently understands a few options only. Bundling of |
59 |
options is not yet supported.</p> |
60 |
<dl> |
61 |
<dt><strong><a name="item__2dq_2c__2d_2dquiet"><strong>-q</strong>, <strong>--quiet</strong></a></strong> |
62 |
|
63 |
<dd> |
64 |
<p>Normally, <strong>urxvtd</strong> outputs the message <code>rxvt-unicode daemon |
65 |
listening on <path></code> after binding to its control socket. This option |
66 |
will suppress this message (errors and warnings will still be logged).</p> |
67 |
</dd> |
68 |
</li> |
69 |
<dt><strong><a name="item__2do_2c__2d_2dopendisplay"><strong>-o</strong>, <strong>--opendisplay</strong></a></strong> |
70 |
|
71 |
<dd> |
72 |
<p>This forces <strong>urxvtd</strong> to open a connection to the current |
73 |
<code>$DISPLAY</code> and keep it open.</p> |
74 |
</dd> |
75 |
<dd> |
76 |
<p>This is useful if you want to bind an instance of <strong>urxvtd</strong> to |
77 |
the lifetime of a specific display/server. If the server does a reset, |
78 |
<strong>urxvtd</strong> will be killed automatically.</p> |
79 |
</dd> |
80 |
</li> |
81 |
<dt><strong><a name="item__2df_2c__2d_2dfork"><strong>-f</strong>, <strong>--fork</strong></a></strong> |
82 |
|
83 |
<dd> |
84 |
<p>This makes <strong>urxvtd</strong> fork after it has bound itself to its control |
85 |
socket.</p> |
86 |
</dd> |
87 |
</li> |
88 |
</dl> |
89 |
<p> |
90 |
</p> |
91 |
<hr /> |
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 |
94 |
script:</p> |
95 |
<pre> |
96 |
B<urxvtd> -q -f -o</pre> |
97 |
<p>This waits till the control socket is available, opens the current display |
98 |
and forks into the background. When you log-out, the server is reset and |
99 |
<strong>urxvtd</strong> is killed.</p> |
100 |
<p> |
101 |
</p> |
102 |
<hr /> |
103 |
<h1><a name="environment">ENVIRONMENT</a></h1> |
104 |
<dl> |
105 |
<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong> |
106 |
|
107 |
<dd> |
108 |
<p>Both <strong>urxvtc</strong> and <strong>urxvtd</strong> use the environment |
109 |
variable <em>RXVT_SOCKET</em> to create a listening socket and to contact |
110 |
the urxvtd, respectively. If the variable is missing, |
111 |
<em>$HOME/.rxvt-unicode-<em><nodename</em> </em>> >>> is used. The variable must |
112 |
specify the absolute path of the socket to create.</p> |
113 |
</dd> |
114 |
</li> |
115 |
<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong> |
116 |
|
117 |
<dd> |
118 |
<p>Only used when the <code>--opendisplay</code> option is specified. Must contain a |
119 |
valid X display name.</p> |
120 |
</dd> |
121 |
</dl> |
122 |
<p> |
123 |
</p> |
124 |
<hr /> |
125 |
<h1><a name="see_also">SEE ALSO</a></h1> |
126 |
<p>urxvt(7), <code>urxvtc(1)</code></p> |
127 |
|
128 |
</body> |
129 |
|
130 |
</html> |