| 1 |
root |
1.1 |
NAME |
| 2 |
|
|
rxvtd - rxvt terminal daemon |
| 3 |
|
|
|
| 4 |
|
|
SYNOPSIS |
| 5 |
|
|
rxvtd [-q|--quiet] [-o|--opendisplay] [-f|--fork] |
| 6 |
|
|
|
| 7 |
|
|
DESCRIPTION |
| 8 |
|
|
This manpage describes the rxvtd daemon, which is the same vt102 |
| 9 |
|
|
terminal emulator as rxvt, but runs as a daemon that can open multiple |
| 10 |
|
|
terminal windows within the same process. |
| 11 |
|
|
|
| 12 |
|
|
You can run it from your X startup scripts, for example, although it is |
| 13 |
|
|
not dependent on a working DISPLAY and, in fact, can open windows on |
| 14 |
|
|
multiple X displays on the same time. |
| 15 |
|
|
|
| 16 |
|
|
Advantages of running a rxvt daemon include faster creation time for |
| 17 |
|
|
terminal windows and a lot of saved memory. |
| 18 |
|
|
|
| 19 |
|
|
The disadvantage is a possible impact on stability - if the main program |
| 20 |
|
|
crashes, all processes in the terminal windows are terminated. For |
| 21 |
|
|
example, as there is no way to cleanly react to abnormal connection |
| 22 |
|
|
closes, "xkill" and server resets/restarts will kill the rxvtd instance |
| 23 |
|
|
including all windows it has opened. |
| 24 |
|
|
|
| 25 |
|
|
OPTIONS |
| 26 |
|
|
rxvtd currently understands a few options only. Bundling of options is |
| 27 |
|
|
not yet supported. |
| 28 |
|
|
|
| 29 |
|
|
-q, --quiet |
| 30 |
|
|
Normally, rxvtd outputs the message "rxvt-unicode daemon listening |
| 31 |
|
|
on <path>" after binding to its control socket. This option will |
| 32 |
root |
1.2 |
suppress this message (errors and warnings will still be logged). |
| 33 |
root |
1.1 |
|
| 34 |
|
|
-o, --opendisplay |
| 35 |
|
|
This forces rxvtd to open a connection to the current $DISPLAY and |
| 36 |
|
|
keep it open. |
| 37 |
|
|
|
| 38 |
|
|
This is useful if you want to bind an instance of rxvtd to the |
| 39 |
|
|
lifetime of a specific display/server. If the server does a reset, |
| 40 |
|
|
rxvtd will be killed automatically. |
| 41 |
|
|
|
| 42 |
|
|
-f, --fork |
| 43 |
|
|
This makes rxvtd fork after it has bound itself to its control |
| 44 |
|
|
socket. |
| 45 |
|
|
|
| 46 |
|
|
EXAMPLES |
| 47 |
|
|
This is a useful invocation of rxvtd in a .xsession-style script: |
| 48 |
|
|
|
| 49 |
|
|
B<rxvtd> -q -f -o |
| 50 |
|
|
|
| 51 |
|
|
This waits till the control socket is available, opens the current |
| 52 |
|
|
display and forks into the background. When you log-out, the server is |
| 53 |
|
|
reset and rxvtd is killed. |
| 54 |
|
|
|
| 55 |
|
|
ENVIRONMENT |
| 56 |
|
|
RXVT_SOCKET |
| 57 |
|
|
Both rxvtc and rxvtd use the environment variable RXVT_SOCKET to |
| 58 |
|
|
create a listening socket and to contact the rxvtd, respectively. If |
| 59 |
|
|
the variable is missing, $HOME/.rxvt-unicode-*<nodename>* is used. |
| 60 |
|
|
|
| 61 |
|
|
DISPLAY |
| 62 |
|
|
Only used when the "--opendisplay" option is specified. Must contain |
| 63 |
|
|
a valid X display name. |
| 64 |
|
|
|
| 65 |
|
|
SEE ALSO |
| 66 |
|
|
rxvt(7), rxvtc(1) |
| 67 |
|
|
|
