… | |
… | |
127 | .\} |
127 | .\} |
128 | .rm #[ #] #H #V #F C |
128 | .rm #[ #] #H #V #F C |
129 | .\" ======================================================================== |
129 | .\" ======================================================================== |
130 | .\" |
130 | .\" |
131 | .IX Title "rxvt 1" |
131 | .IX Title "rxvt 1" |
132 | .TH rxvt 1 "2005-07-07" "5.6" "RXVT-UNICODE" |
132 | .TH rxvt 1 "2006-02-02" "7.5" "RXVT-UNICODE" |
133 | .SH "NAME" |
133 | .SH "NAME" |
134 | @@RXVT_NAME@@c \- control the @@RXVT_NAME@@d daemon |
134 | @@RXVT_NAME@@c \- control the @@RXVT_NAME@@d daemon |
135 | .SH "SYNOPSIS" |
135 | .SH "SYNOPSIS" |
136 | .IX Header "SYNOPSIS" |
136 | .IX Header "SYNOPSIS" |
137 | \&\fB@@RXVT_NAME@@c\fR [same options as for @@RXVT_NAME@@] |
137 | \&\fB@@RXVT_NAME@@c\fR [same options as for @@RXVT_NAME@@] |
… | |
… | |
146 | .IX Header "OPTIONS" |
146 | .IX Header "OPTIONS" |
147 | All options that are valid for \fB@@RXVT_NAME@@\fR are valid for |
147 | All options that are valid for \fB@@RXVT_NAME@@\fR are valid for |
148 | \&\fB@@RXVT_NAME@@c\fR, too. Please note that all options are currently |
148 | \&\fB@@RXVT_NAME@@c\fR, too. Please note that all options are currently |
149 | interpreted in the context of the daemon process, which makes a difference |
149 | interpreted in the context of the daemon process, which makes a difference |
150 | for options that specify a file descriptor (such as \fB\-pty\-fd\fR). |
150 | for options that specify a file descriptor (such as \fB\-pty\-fd\fR). |
|
|
151 | .SH "EXIT STATUS" |
|
|
152 | .IX Header "EXIT STATUS" |
|
|
153 | If everything went well, @@RXVT_NAME@@c returns with an exit status of \f(CW0\fR. |
|
|
154 | If contacting the daemon fails, it exits with the exit status \f(CW2\fR. In all other error |
|
|
155 | cases it returns with status \f(CW1\fR. |
|
|
156 | .PP |
|
|
157 | This can be used to implement auto-starting behaviour, by checking for an |
|
|
158 | exit status of \f(CW2\fR, running \f(CW\*(C`@@RXVT_NAME@@d \-f \-q\*(C'\fR and retrying the call |
|
|
159 | to @@RXVT_NAME@@c. |
151 | .SH "ENVIRONMENT" |
160 | .SH "ENVIRONMENT" |
152 | .IX Header "ENVIRONMENT" |
161 | .IX Header "ENVIRONMENT" |
153 | All environment variables of the current process will be made available |
162 | All environment variables of the current process will be made available |
154 | to the new instance, and will be interpreted as if \fB@@RXVT_NAME@@\fR were |
163 | to the new instance, and will be interpreted as if \fB@@RXVT_NAME@@\fR were |
155 | started directly. |
164 | started directly. |
156 | .IP "\fB\s-1RXVT_SOCKET\s0\fR" 4 |
165 | .IP "\fB\s-1RXVT_SOCKET\s0\fR" 4 |
157 | .IX Item "RXVT_SOCKET" |
166 | .IX Item "RXVT_SOCKET" |
158 | Both @@RXVT_NAME@@c and @@RXVT_NAME@@d use the environment variable |
167 | Both @@RXVT_NAME@@c and @@RXVT_NAME@@d use the environment variable |
159 | \&\fI\s-1RXVT_SOCKET\s0\fR to create a listening socket and to contact |
168 | \&\fI\s-1RXVT_SOCKET\s0\fR to create a listening socket and to contact the |
160 | the @@RXVT_NAME@@d, respectively. If the variable is missing, |
169 | @@RXVT_NAME@@d, respectively. If the variable is missing, |
161 | \&\fI$HOME/.rxvt\-unicode\-\fI<nodename>\fI\fR is used. |
170 | \&\fI$HOME/.rxvt\-unicode\-\fI<nodename>\fI\fR is used. The variable must |
|
|
171 | specify the absolute path of the socket to create. |
162 | .SH "SEE ALSO" |
172 | .SH "SEE ALSO" |
163 | .IX Header "SEE ALSO" |
173 | .IX Header "SEE ALSO" |
164 | @@RXVT_NAME@@(7), @@RXVT_NAME@@d(1) |
174 | @@RXVT_NAME@@(7), @@RXVT_NAME@@d(1) |