ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvtd.1.txt
(Generate patch)

Comparing rxvt-unicode/doc/rxvtd.1.txt (file contents):
Revision 1.2 by root, Wed Jul 13 02:53:54 2005 UTC vs.
Revision 1.4 by root, Mon Jul 17 19:20:29 2006 UTC

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

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines