All options that are valid for urxvt are valid for urxvtc, too. Please note that options are interpreted in the context of the daemon process. However, as current working directory, process environment and any file descriptor (e.g. for "-pty-fd") are preserved, this rarely makes a difference.
This can be used to implement auto-starting behaviour, by checking for an exit status of 2, running "urxvtd -f -q" and retrying the call to urxvtc, like this:
#!/bin/sh urxvtc "$@" if [ $? -eq 2 ]; then urxvtd -q -o -f urxvtc "$@" fi
- Both urxvtc and urxvtd use the environment variable RXVT_SOCKET to create a listening socket and to contact the urxvtd, respectively. If the variable is missing, $HOME/.urxvt/urxvtd-<nodename> is used. The variable must specify the absolute path of the socket to create.