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