xfs
X font server
1. xfs.1.man
Manpage of XFS
XFS
Section: User Commands (1)Updated: xfs 1.0.4
Index Return to Main Contents
NAME
xfs - X font serverSYNOPSIS
xfs [-config configuration_file] [-daemon] [-droppriv] [-ls listen_socket] [-nodaemon] [-port tcp_port] [-user username]DESCRIPTION
Xfs is the X Window System font server. It supplies fonts to X Window System display servers.
STARTING THE SERVER
The server is usually run by a system administrator, and started via boot files like /etc/rc.local. Users may also wish to start private font servers for specific sets of fonts.OPTIONS
- -config configuration_file
- Specifies the configuration file the font server will use. If this parameter is not specified, the default file, /etc/X11/fs/config will be used.
- -ls listen_socket
- Specifies a file descriptor which is already set up to be used as the listen socket. This option is only intended to be used by the font server itself when automatically spawning another copy of itself to handle additional connections.
- -port tcp_port
- Specifies the TCP port number on which the server will listen for connections. The default port number is 7100.
- -daemon
- Instructs xfs to fork and go into the background automatically at startup If this option is not specified, xfs will run as a regular process (unless xfs was built to daemonize by default).
- -droppriv
- If specified, xfs will attempt to run as user and group xfs (unless the -user option is used). This has been implemented for security reasons, as xfs may have undiscovered buffer overflows or other paths for possible exploit, both local and remote. With this option, you may also wish to specify "no-listen = tcp" in the config file, which ensures that xfs will not to use a TCP port at all.
- -nodaemon
- When xfs is built to daemonize (run in the background) by default, this prevents that and starts xfs up as a regular process.
- -user username
- This is equivalent to -droppriv except that xfs will run as user username.
SIGNALS
- SIGTERM
- This causes the font server to exit cleanly.
- SIGUSR1
- This signal is used to cause the server to re-read its configuration file.
- SIGUSR2
- This signal is used to cause the server to flush any cached data it may have.
- SIGHUP
- This signal is used to cause the server to reset, closing all active connections and re-reading the configuration file.
CONFIGURATION
The configuration language is a list of keyword and value pairs. Each keyword is followed by an '=' and then the desired value.Recognized keywords include:
- catalogue (list of string)
- Ordered list of font path element names. Use of the keyword "catalogue" is very misleading at present, the current implementation only supports a single catalogue ("all"), containing all of the specified fonts.
- alternate-servers (list of string)
- List of alternate servers for this font server.
- client-limit (cardinal)
- Number of clients this font server will support before refusing service. This is useful for tuning the load on each individual font server.
- clone-self (boolean)
- Whether this font server should attempt to clone itself when it reachs the client-limit.
- default-point-size (cardinal)
- The default pointsize (in decipoints) for fonts that don't specify. The default is 120.
- default-resolutions (list of resolutions)
- Resolutions the server supports by default. This information may be used as a hint for pre-rendering, and substituted for scaled fonts which do not specify a resolution. A resolution is a comma-separated pair of x and y resolutions in pixels per inch. Multiple resolutions are separated by commas.
- error-file (string)
- Filename of the error file. All warnings and errors will be logged here.
- no-listen (trans-type)
- Disable a transport type. For example, TCP/IP connections can be disabled with no-listen tcp
- port (cardinal)
- TCP port on which the server will listen for connections.
- use-syslog (boolean)
- Whether syslog(3) (on supported systems) is to be used for errors.
- deferglyphs (string)
- Set the mode for delayed fetching and caching of glyphs. Value is "none", meaning deferred glyphs is disabled, "all", meaning it is enabled for all fonts, and "16", meaning it is enabled only for 16-bits fonts.
EXAMPLE
#
# sample font server configuration file
#
# allow a max of 10 clients to connect to this font server
client-limit = 10
# when a font server reaches its limit, start up a new one
clone-self = on
# alternate font servers for clients to use
alternate-servers = hansen:7101,hansen:7102
# where to look for fonts
# the first is a set of Speedo outlines, the second is a set of
# misc bitmaps and the last is a set of 100dpi bitmaps
#
catalogue = /usr/X11R6/lib/X11/fonts/speedo,
/usr/X11R6/lib/X11/fonts/misc,
/usr/X11R6/lib/X11/fonts/100dpi/
# in 12 points, decipoints
default-point-size = 120
# 100 x 100 and 75 x 75
default-resolutions = 100,100,75,75
use-syslog = off
FONT SERVER NAMES
One of the following forms can be used to name a font server that accepts TCP connections:
tcp/hostname:port
tcp/hostname:port/cataloguelist
The hostname specifies the name (or decimal numeric address) of the machine on which the font server is running. The port is the decimal TCP port on which the font server is listening for connections. The cataloguelist specifies a list of catalogue names, with '+' as a separator.
Examples: tcp/fs.x.org:7100, tcp/18.30.0.212:7101/all.
One of the following forms can be used to name a font server that accepts DECnet connections:
decnet/nodename::font$objname
decnet/nodename::font$objname/cataloguelist
The nodename specifies the name (or decimal numeric address) of the machine on which the font server is running. The objname is a normal, case-insensitive DECnet object name. The cataloguelist specifies a list of catalogue names, with '+' as a separator.
Examples: DECnet/SRVNOD::FONT$DEFAULT, decnet/44.70::font$special/symbols.
SEE ALSO
X(7), The X Font Service Protocol,Font server implementation overview
BUGS
Multiple catalogues should be supported.AUTHORS
Dave Lemke, Network Computing Devices, IncKeith Packard, Massachusetts Institute of Technology
Index
- NAME
- SYNOPSIS
- DESCRIPTION
- STARTING THE SERVER
- OPTIONS
- SIGNALS
- CONFIGURATION
- EXAMPLE
- FONT SERVER NAMES
- SEE ALSO
- BUGS
- AUTHORS
This document was created by man2html using the manual pages.
Time: 23:23:00 GMT, July 09, 2008
2. xfs.5.man
Manpage of xfs
xfs
Section: File Formats (5)Index Return to Main Contents
NAME
xfs - layout of the XFS filesystemDESCRIPTION
An XFS filesystem can reside on a regular disk partition or on a logical volume. An XFS filesystem has up to three parts: a data section, a log section, and a realtime section. Using the default mkfs.xfs(8) options, the realtime section is absent, and the log area is contained within the data section. The log section can be either separate from the data section or contained within it. The filesystem sections are divided into a certain number of blocks, whose size is specified at mkfs.xfs(8) time with the -b option.The data section contains all the filesystem metadata (inodes, directories, indirect blocks) as well as the user file data for ordinary (non-realtime) files and the log area if the log is internal to the data section. The data section is divided into a number of allocation groups. The number and size of the allocation groups are chosen by mkfs.xfs(8) so that there is normally a small number of equal-sized groups. The number of allocation groups controls the amount of parallelism available in file and block allocation. It should be increased from the default if there is sufficient memory and a lot of allocation activity. The number of allocation groups should not be set very high, since this can cause large amounts of CPU time to be used by the filesystem, especially when the filesystem is nearly full. More allocation groups are added (of the original size) when xfs_growfs(8) is run.
The log section (or area, if it is internal to the data section) is used to store changes to filesystem metadata while the filesystem is running until those changes are made to the data section. It is written sequentially during normal operation and read only during mount. When mounting a filesystem after a crash, the log is read to complete operations that were in progress at the time of the crash.
The realtime section is used to store the data of realtime files. These files had an attribute bit set through xfsctl(3) after file creation, before any data was written to the file. The realtime section is divided into a number of extents of fixed size (specified at mkfs.xfs(8) time). Each file in the realtime section has an extent size that is a multiple of the realtime section extent size.
Each allocation group contains several data structures. The first sector contains the superblock. For allocation groups after the first, the superblock is just a copy and is not updated after mkfs.xfs(8). The next three sectors contain information for block and inode allocation within the allocation group. Also contained within each allocation group are data structures to locate free blocks and inodes; these are located through the header structures.
Each XFS filesystem is labeled with a Universal Unique Identifier (UUID). The UUID is stored in every allocation group header and is used to help distinguish one XFS filesystem from another, therefore you should avoid using dd(1) or other block-by-block copying programs to copy XFS filesystems. If two XFS filesystems on the same machine have the same UUID, xfsdump(8) may become confused when doing incremental and resumed dumps. xfsdump(8) and xfsrestore(8) are recommended for making copies of XFS filesystems.
OPERATIONS
Some functionality specific to the XFS filesystem is accessible to applications through the xfsctl(3) and by-handle (see open_by_handle(3)) interfaces.MOUNT OPTIONS
Refer to the mount(8) manual entry for descriptions of the individual XFS mount options.SEE ALSO
xfsctl(3), mount(8), mkfs.xfs(8), xfs_info(8), xfs_admin(8), xfsdump(8), xfsrestore(8).
Index
This document was created by man2html using the manual pages.
Time: 23:23:00 GMT, July 09, 2008
