Section 7: overview, conventions, and miscellany
gammu-smsd-mysql – gammu-smsd(1) backend using MySQL database server as a message storage Description gammu-smsd(1) supports several backends. Actual backend is chosen in a config file gammu-smsdrc(5). MYSQL backend stores all data in a MySQL database server, which parameters are defined by configuration (see gammu-smsdrc(5) for description of configuration options). For tables description see gammu-smsd-tables(7). See…
gammu-smsd-files – gammu-smsd(1) backend using filesystem as a message storage Description gammu-smsd(1) supports several backends. Actual backend is chosen in a config file gammu-smsdrc(5). FILES backend stores all data on a filesystem in folders defined by configuration (see gammu-smsdrc(5) for description of configuration options). Limitation FILES backend does not support gammu-smsd-inject(1) program. This support might…
gammu-smsd-dbi – gammu-smsd(1) backend using DBI abstraction layer to use any supported database as a message storage Description gammu-smsd(1) supports several backends. Actual backend is chosen in a config file gammu-smsdrc(5). DBI backend stores all data in any database supported by libdbi, which parameters are defined by configuration (see gammu-smsdrc(5) for description of configuration options)….
futex – fast user-space locking Synopsis #include <linux/futex.h> Description The Linux kernel provides futexes ("Fast user-space mutexes") as a building block for fast user-space locking and semaphores. Futexes are very basic and lend themselves well for building higher-level locking abstractions such as mutexes, condition variables, read-write locks, barriers, and semaphores. Most programmers will in fact…
feature_test_macros – feature test macros Description Feature test macros allow the programmer to control the definitions that are exposed by system header files when a program is compiled. NOTE: In order to be effective, a feature test macro must be defined before including any header files. This can be done either in the compilation command…
frysk – The Frysk Debugging, Tracing, and Monitoring Tool Suite Description The Frysk Tool Suite provides a collection of command line and gnome utilities for the debugging, tracing, and monitoring of user programs. See Also funit(8) fauxv(1) fcatch(1) fcore(1) fdebuginfo(1) ferror(1) fexe(1) fhpd(1) fmaps(1) fparser(1) fstack(1) fstep(1) ftrace(1) fdebugrpm(1) Bugs Report bugs to m[blue]http://sourceware.org/fryskm[]
frontend-spec – interface between jw and its frontends Description jw(1) calls frontends like frontends/docbook to get the informations specific to a given input format. The frontend knows which information to return from the first command line parameter. It gets all necessary data via environment variables ready to use. This document describes that command line parameter…
FreeIPMI – FreeIPMI overview Introduction FreeIPMI provides in-band and out-of-band IPMI software based on the IPMI v1.5/2.0 specification. What is IPMI? The IPMI specification defines a set of interfaces for platform management and is implemented by a number vendors for system management. The features of IPMI that most users will be interested in are sensor…
filter – cups file conversion filter interface Synopsis filter job user title num – copies options [filename ] #include <cups/cups.h> ssize_t cupsBackChannelRead(char *buffer, size_t bytes, double timeout); cups_sc_status_t cupsSideChannelDoRequest(cups_sc_command_t command, char *data, int *datalen, double timeout); #include <cups/ppd.h> const char *cupsGetOption(const char *name, int num_options, cups_option_t *options); int cupsMarkOptions(ppd_file_t *ppd, int num_options, cups_option_t *options); int…
filesystem – event signalling that filesystems have been mounted Synopsis filesystem [ENV]… Description The filesystem event is generated by the mountall(8) daemon after it has mounted all filesystems listed in fstab(5). mountall(8) emits this event as an informational signal, services and tasks started or stopped by this event will do so in parallel with other…
file-hierarchy – File system hierarchy overview Description Operating systems using the systemd(1) system and service manager are organized based on a file system hierarchy inspired by UNIX, more specifically the hierarchy described in the m[blue]File System Hierarchym[][1] specification and hier(7), with various extensions, partially documented in the m[blue]XDG Base Directory Specificationm[][2] and m[blue]XDG User Directoriesm[][3]….
file – event signalling that a file has changed Synopsis file FILE=PATH EVENT=TYPE [MATCH=PATH] Description The file event is generated by the upstart-file-bridge(8) daemon when a file whose details match the file event condition and environment specified in a job’s start on or stop on stanza is modified. The FILE and EVENT environment variables will…
fifo – first-in first-out special file, named pipe Description A FIFO special file (a named pipe) is similar to a pipe, except that it is accessed as part of the filesystem. It can be opened by multiple processes for reading or writing. When processes are exchanging data via the FIFO, the kernel passes all data…
fi_verbs – The Verbs Fabric Provider Overview The verbs provider enables applications using OFI to be run over any verbs hardware (Infiniband, iWarp, etc). It uses the Linux Verbs API for network transport and provides a translation of OFI calls to appropriate verbs API calls. It uses librdmacm for communication management and libibverbs for other…
fi_udp – The UDP Fabric Provider Overview The UDP provider is a basic provider that can be used on any system that supports UDP sockets. The provider is not intended to provide performance improvements over regular TCP sockets, but rather to allow application and provider developers to write, test, and debug their code. The UDP…
fi_sockets – The Sockets Fabric Provider Overview The sockets provider is a general purpose provider that can be used on any system that supports TCP sockets. The provider is not intended to provide performance improvements over regular TCP sockets, but rather to allow developers to write, test, and debug application code even on platforms that…
fi_psm – The PSM Fabric Provider Overview The psm provider runs over the PSM 1.x interface that is currently supported by the Intel TrueScale Fabric. PSM provides tag-matching message queue functions that are optimized for MPI implementations. PSM also has limited Active Message support, which is not officially published but is quite stable and well…
fi_provider – Fabric Interface Providers Overview Conceptually, a fabric provider may be viewed as a local hardware NIC driver, though a provider is not limited by this definition. The first component of libfabric is a general purpose framework that is capable of handling different types of fabric hardware. All fabric hardware devices and their software…
fi_direct – Direct fabric provider access Synopsis -DFABRIC_DIRECT #define FABRIC_DIRECT Fabric direct provides a mechanism for applications to compile against a specific fabric providers without going through the libfabric framework or function vector tables. This allows for extreme optimization via function inlining at the cost of supporting multiple providers or different versions of the same…
fedfs – The Linux Federated File System implementation Description RFC 5716 introduces the Federated File System (FedFS, for short). FedFS is an extensible standardized mechanism by which system administrators construct a coherent namespace across multiple fileservers using file system referrals. A file system referral is like a symbolic link to another file system share, but…