… | |
… | |
15 | contacting the daemon. |
15 | contacting the daemon. |
16 | |
16 | |
17 | =head1 OPTIONS |
17 | =head1 OPTIONS |
18 | |
18 | |
19 | All options that are valid for B<@@RXVT_NAME@@> are valid for |
19 | All options that are valid for B<@@RXVT_NAME@@> are valid for |
20 | B<@@RXVT_NAME@@c>, too. Please note that all options are currently |
20 | B<@@RXVT_NAME@@c>, too. Please note that options are interpreted in the |
21 | interpreted in the context of the daemon process, which makes a difference |
21 | context of the daemon process. However, as current working directory, |
22 | for options that specify a file descriptor (such as B<-pty-fd>). |
22 | process environment and any file descriptor (e.g. for C<-pty-fd>) are |
|
|
23 | preserved, this rarely makes a difference. |
|
|
24 | |
|
|
25 | =head1 EXIT STATUS |
|
|
26 | |
|
|
27 | If everything went well, @@RXVT_NAME@@c returns with an exit status of C<0>. |
|
|
28 | If contacting the daemon fails, it exits with the exit status C<2>. In all other error |
|
|
29 | cases it returns with status C<1>. |
|
|
30 | |
|
|
31 | This can be used to implement auto-starting behaviour, by checking for an |
|
|
32 | exit status of C<2>, running C<@@RXVT_NAME@@d -f -q> and retrying the call |
|
|
33 | to @@RXVT_NAME@@c, like this: |
|
|
34 | |
|
|
35 | #!/bin/sh |
|
|
36 | @@RXVT_NAME@@c "$@" |
|
|
37 | if [ $? -eq 2 ]; then |
|
|
38 | @@RXVT_NAME@@d -q -o -f |
|
|
39 | @@RXVT_NAME@@c "$@" |
|
|
40 | fi |
23 | |
41 | |
24 | =head1 ENVIRONMENT |
42 | =head1 ENVIRONMENT |
25 | |
43 | |
26 | All environment variables of the current process will be made available |
44 | All environment variables of the current process will be made available |
27 | to the new instance, and will be interpreted as if B<@@RXVT_NAME@@> were |
45 | to the new instance, and will be interpreted as if B<@@RXVT_NAME@@> were |
… | |
… | |
30 | =over 4 |
48 | =over 4 |
31 | |
49 | |
32 | =item B<RXVT_SOCKET> |
50 | =item B<RXVT_SOCKET> |
33 | |
51 | |
34 | Both @@RXVT_NAME@@c and @@RXVT_NAME@@d use the environment variable |
52 | Both @@RXVT_NAME@@c and @@RXVT_NAME@@d use the environment variable |
35 | F<RXVT_SOCKET> to create a listening socket and to contact |
53 | F<RXVT_SOCKET> to create a listening socket and to contact the |
36 | the @@RXVT_NAME@@d, respectively. If the variable is missing, |
54 | @@RXVT_NAME@@d, respectively. If the variable is missing, |
37 | F<<< $HOME/.rxvt-unicode-I<< <nodename> >> >>> is used. |
55 | F<<< $HOME/.rxvt-unicode-I<< <nodename> >> >>> is used. The variable must |
|
|
56 | specify the absolute path of the socket to create. |
38 | |
57 | |
39 | =back |
58 | =back |
40 | |
59 | |
41 | =head1 SEE ALSO |
60 | =head1 SEE ALSO |
42 | |
61 | |