--- rxvt-unicode/doc/rxvtc.1.man.in	2005/07/07 19:41:22	1.1
+++ rxvt-unicode/doc/rxvtc.1.man.in	2006/02/02 00:24:14	1.3
@@ -129,7 +129,7 @@
 .\" ========================================================================
 .\"
 .IX Title "rxvt 1"
-.TH rxvt 1 "2005-07-07" "5.6" "RXVT-UNICODE"
+.TH rxvt 1 "2006-02-02" "7.5" "RXVT-UNICODE"
 .SH "NAME"
 @@RXVT_NAME@@c \- control the @@RXVT_NAME@@d daemon
 .SH "SYNOPSIS"
@@ -148,6 +148,15 @@
 \&\fB@@RXVT_NAME@@c\fR, too. Please note that all options are currently
 interpreted in the context of the daemon process, which makes a difference
 for options that specify a file descriptor (such as \fB\-pty\-fd\fR).
+.SH "EXIT STATUS"
+.IX Header "EXIT STATUS"
+If everything went well, @@RXVT_NAME@@c returns with an exit status of \f(CW0\fR.
+If contacting the daemon fails, it exits with the exit status \f(CW2\fR. In all other error
+cases it returns with status \f(CW1\fR.
+.PP
+This can be used to implement auto-starting behaviour, by checking for an
+exit status of \f(CW2\fR, running \f(CW\*(C`@@RXVT_NAME@@d \-f \-q\*(C'\fR and retrying the call
+to @@RXVT_NAME@@c.
 .SH "ENVIRONMENT"
 .IX Header "ENVIRONMENT"
 All environment variables of the current process will be made available
@@ -156,9 +165,10 @@
 .IP "\fB\s-1RXVT_SOCKET\s0\fR" 4
 .IX Item "RXVT_SOCKET"
 Both @@RXVT_NAME@@c and @@RXVT_NAME@@d use the environment variable
-\&\fI\s-1RXVT_SOCKET\s0\fR to create a listening socket and to contact
-the @@RXVT_NAME@@d, respectively. If the variable is missing,
-\&\fI$HOME/.rxvt\-unicode\-\fI<nodename>\fI\fR is used.
+\&\fI\s-1RXVT_SOCKET\s0\fR to create a listening socket and to contact the
+@@RXVT_NAME@@d, respectively. If the variable is missing,
+\&\fI$HOME/.rxvt\-unicode\-\fI<nodename>\fI\fR is used.  The variable must
+specify the absolute path of the socket to create.
 .SH "SEE ALSO"
 .IX Header "SEE ALSO"
 @@RXVT_NAME@@(7), @@RXVT_NAME@@d(1)