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