| 1 |
<?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 |
<head> |
| 5 |
<title>urxvtd</title> |
| 6 |
<meta name="description" content="Pod documentation for urxvtd" /> |
| 7 |
<meta name="inputfile" content="<standard input>" /> |
| 8 |
<meta name="outputfile" content="<standard output>" /> |
| 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> |
| 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 |
<!-- INDEX END --> |
| 27 |
|
| 28 |
<h1 id="NAME">NAME</h1><p><a href="#TOP" class="toplink">Top</a></p> |
| 29 |
<div id="NAME_CONTENT"> |
| 30 |
<p>urxvtd - urxvt terminal daemon</p> |
| 31 |
|
| 32 |
</div> |
| 33 |
<h1 id="SYNOPSIS">SYNOPSIS</h1><p><a href="#TOP" class="toplink">Top</a></p> |
| 34 |
<div id="SYNOPSIS_CONTENT"> |
| 35 |
<p><strong>urxvtd</strong> [-q|--quiet] [-o|--opendisplay] [-f|--fork]</p> |
| 36 |
<p><strong>urxvtd</strong> -q -o -f # for .xsession use</p> |
| 37 |
|
| 38 |
</div> |
| 39 |
<h1 id="DESCRIPTION">DESCRIPTION</h1><p><a href="#TOP" class="toplink">Top</a></p> |
| 40 |
<div id="DESCRIPTION_CONTENT"> |
| 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 |
|
| 55 |
</div> |
| 56 |
<h1 id="OPTIONS">OPTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p> |
| 57 |
<div id="OPTIONS_CONTENT"> |
| 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>-q</strong>, <strong>--quiet</strong></dt> |
| 62 |
<dd> |
| 63 |
<p>Normally, <strong>urxvtd</strong> outputs the message <code>rxvt-unicode daemon |
| 64 |
listening on <path></code> after binding to its control socket. This option |
| 65 |
will suppress this message (errors and warnings will still be logged).</p> |
| 66 |
</dd> |
| 67 |
<dt><strong>-o</strong>, <strong>--opendisplay</strong></dt> |
| 68 |
<dd> |
| 69 |
<p>This forces <strong>urxvtd</strong> to open a connection to the current |
| 70 |
<code>$DISPLAY</code> and keep it open.</p> |
| 71 |
<p>This is useful if you want to bind an instance of <strong>urxvtd</strong> to |
| 72 |
the lifetime of a specific display/server. If the server does a reset, |
| 73 |
<strong>urxvtd</strong> will be killed automatically.</p> |
| 74 |
</dd> |
| 75 |
<dt><strong>-f</strong>, <strong>--fork</strong></dt> |
| 76 |
<dd> |
| 77 |
<p>This makes <strong>urxvtd</strong> fork after it has bound itself to its control |
| 78 |
socket.</p> |
| 79 |
</dd> |
| 80 |
</dl> |
| 81 |
|
| 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>urxvtd</strong> in a <cite>.xsession</cite>-style |
| 86 |
script:</p> |
| 87 |
<pre> urxvtd -q -f -o |
| 88 |
|
| 89 |
</pre> |
| 90 |
<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 |
<strong>urxvtd</strong> is killed.</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 |
| 101 |
variable <cite>RXVT_SOCKET</cite> to create a listening socket and to contact |
| 102 |
the urxvtd, respectively. If the variable is missing, |
| 103 |
<cite>$HOME/.rxvt-unicode-<i><nodename></i></cite> is used. The variable must |
| 104 |
specify 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 |
| 109 |
valid 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) |
| 117 |
</p> |
| 118 |
|
| 119 |
</div> |
| 120 |
</div></body> |
| 121 |
</html> |
