--- rxvt-unicode/doc/rxvtd.1.html 2005/12/17 20:55:45 1.3 +++ rxvt-unicode/doc/rxvtd.1.html 2006/07/17 19:20:29 1.4 @@ -1,7 +1,9 @@ +
-
rxvtd - rxvt terminal daemon
+urxvtd - urxvt terminal daemon
rxvtd [-q|--quiet] [-o|--opendisplay] [-f|--fork]
+urxvtd [-q|--quiet] [-o|--opendisplay] [-f|--fork]
This manpage describes the rxvtd daemon, which is the same vt102 -terminal emulator as rxvt, but runs as a daemon that can open +
This manpage describes the urxvtd daemon, which is the same vt102 +terminal emulator as urxvt, but runs as a daemon that can open multiple terminal windows within the same process.
You can run it from your X startup scripts, for example, although it is not dependent on a working DISPLAY and, in fact, can open windows on multiple X displays on the same time.
-Advantages of running a rxvt daemon include faster creation time +
Advantages of running a urxvt daemon include faster creation time for terminal windows and a lot of saved memory.
The disadvantage is a possible impact on stability - if the
main program crashes, all processes in the terminal windows are
terminated. For example, as there is no way to cleanly react to abnormal
connection closes, xkill
and server resets/restarts will kill the
-rxvtd instance including all windows it has opened.
rxvtd currently understands a few options only. Bundling of +
urxvtd currently understands a few options only. Bundling of options is not yet supported.
rxvt-unicode daemon
+Normally, urxvtd outputs the message rxvt-unicode daemon
listening on <path>
after binding to its control socket. This option
-will suppress this message (errors and warnings will still be logged).
+will suppress this message (errors and warnings will still be logged).
$DISPLAY
and keep it open.
+This forces urxvtd to open a connection to the current
+$DISPLAY
and keep it open.
This is useful if you want to bind an instance of rxvtd to +
This is useful if you want to bind an instance of urxvtd to the lifetime of a specific display/server. If the server does a reset, -rxvtd will be killed automatically.
+urxvtd will be killed automatically.This makes urxvtd fork after it has bound itself to its control +socket.
This is a useful invocation of rxvtd in a .xsession-style +
This is a useful invocation of urxvtd in a .xsession-style script:
- B<rxvtd> -q -f -o+ B<urxvtd> -q -f -o
This waits till the control socket is available, opens the current display and forks into the background. When you log-out, the server is reset and -rxvtd is killed.
+urxvtd is killed.
Both urxvtc and urxvtd use the environment variable RXVT_SOCKET to create a listening socket and to contact -the rxvtd, respectively. If the variable is missing, +the urxvtd, respectively. If the variable is missing, $HOME/.rxvt-unicode-<nodename > >>> is used. The variable must -specify the absolute path of the socket to create. +specify the absolute path of the socket to create.
--opendisplay
option is specified. Must contain a
-valid X display name.
+Only used when the --opendisplay
option is specified. Must contain a
+valid X display name.
rxvt(7), rxvtc(1)
urxvt(7), urxvtc(1)