Skip to content

Latest commit

 

History

History
105 lines (68 loc) · 3.27 KB

rxvtd.1.pod

File metadata and controls

105 lines (68 loc) · 3.27 KB
Raw

NAME

@@RXVT_NAME@@d - @@RXVT_NAME@@ terminal daemon

SYNOPSIS

@@RXVT_NAME@@d [-q|--quiet] [-o|--opendisplay] [-f|--fork] [-m|--mlock]

@@RXVT_NAME@@d -q -o -f # for .xsession use

DESCRIPTION

This manpage describes the @@RXVT_NAME@@d daemon, which is the same vt102 terminal emulator as @@RXVT_NAME@@, but runs as a daemon that can open multiple terminal windows within the same process.

You can run it from your X startup scripts, for example, although it is not dependent on a working DISPLAY and, in fact, can open windows on multiple X displays on the same time.

Advantages of running a @@RXVT_NAME@@ daemon include faster creation time for terminal windows and a lot of saved memory.

The disadvantage is a possible impact on stability - if the main program crashes, all processes in the terminal windows are terminated. For example, as there is no way to cleanly react to abnormal connection closes, xkill and server resets/restarts will kill the @@RXVT_NAME@@d instance including all windows it has opened.

OPTIONS

@@RXVT_NAME@@d currently understands a few options only. Bundling of options is not yet supported.

-q, --quiet

Normally, @@RXVT_NAME@@d outputs the message rxvt-unicode daemon listening on <path> after binding to its control socket. This option will suppress this message (errors and warnings will still be logged).

-o, --opendisplay

This forces @@RXVT_NAME@@d to open a connection to the current $DISPLAY and keep it open.

This is useful if you want to bind an instance of @@RXVT_NAME@@d to the lifetime of a specific display/server. If the server does a reset, @@RXVT_NAME@@d will be killed automatically.

-f, --fork

This makes @@RXVT_NAME@@d fork after it has bound itself to its control socket.

-m, --mlock

This makes @@RXVT_NAME@@d call mlockall(2) on itself. This locks @@RXVT_NAME@@d in RAM and prevents it from being swapped out to disk, at the cost of consuming a lot more memory on most operating systems.

Note: In order to use this feature, your system administrator must have set your user's RLIMIT_MEMLOCK to a size greater than or equal to the size of the @@RXVT_NAME@@d binary (or to unlimited). See /etc/security/limits.conf.

Note 2: There is a known bug in glibc (possibly fixed in 2.8 and later versions) where calloc returns non-zeroed memory when mlockall is in effect. If you experience crashes or other odd behaviour while using --mlock, try it without it.

EXAMPLES

This is a useful invocation of @@RXVT_NAME@@d in a .xsession-style script:

@@RXVT_NAME@@d -q -f -o

This waits till the control socket is available, opens the current display and forks into the background. When you log-out, the server is reset and @@RXVT_NAME@@d is killed.

ENVIRONMENT

RXVT_SOCKET

Both @@RXVT_NAME@@c and @@RXVT_NAME@@d use the environment variable RXVT_SOCKET to create a listening socket and to contact the @@RXVT_NAME@@d, respectively. If the variable is missing then $HOME/.rxvt-unicode-<nodename> is used.

DISPLAY

Only used when the --opendisplay option is specified. Must contain a valid X display name.

SEE ALSO

@@RXVT_NAME@@(7), @@RXVT_NAME@@c(1)