Section 7: overview, conventions, and miscellany
stopping – event signalling that a job is stopping Synopsis stopping JOB=JOB INSTANCE=INSTANCE RESULT=RESULT [PROCESS=PROCESS] [EXIT_STATUS=STATUS] [EXIT_SIGNAL=SIGNAL] [ENV]… Description The stopping event is generated by the Upstart init(8) daemon when an instance of a job begins stopping. The JOB environment variable contains the job name, and the INSTANCE environment variable contains the instance name which…
stopped – event signalling that a job has stopped Synopsis stopped JOB=JOB INSTANCE=INSTANCE RESULT=RESULT [PROCESS=PROCESS] [EXIT_STATUS=STATUS] [EXIT_SIGNAL=SIGNAL] [ENV]… Description The stopped event is generated by the Upstart init(8) daemon when an instance of a job has stopped. The JOB environment variable contains the job name, and the INSTANCE environment variable contains the instance name which…
stonithd – Options available for all stonith resources Synopsis [priority=integer] [pcmk_host_argument=string] [pcmk_host_map=string] [pcmk_host_list=string] [pcmk_host_check=string] [pcmk_delay_max=time] [pcmk_action_limit=integer] [pcmk_reboot_action=string] [pcmk_reboot_timeout=time] [pcmk_reboot_retries=integer] [pcmk_off_action=string] [pcmk_off_timeout=time] [pcmk_off_retries=integer] [pcmk_list_action=string] [pcmk_list_timeout=time] [pcmk_list_retries=integer] [pcmk_monitor_action=string] [pcmk_monitor_timeout=time] [pcmk_monitor_retries=integer] [pcmk_status_action=string] [pcmk_status_timeout=time] [pcmk_status_retries=integer] Description This is a fake resource that details the instance attributes handled by stonithd. Supported Parameters priority = integer [0] The priority of the…
startup – event signalling system startup Synopsis startup [ENV]… Description The startup event is generated by the Upstart init(8) daemon after it has completed its own initialisation and is the signal that the rest of the system may be started. Typically this will involve checking and mounting the partitions and drives that form the filesystem,…
starting – event signalling that a job is starting Synopsis starting JOB=JOB INSTANCE=INSTANCE [ENV]… Description The starting event is generated by the Upstart init(8) daemon when a new instance of a job begins starting. The JOB environment variable contains the job name, and the INSTANCE environment variable contains the instance name which will be empty…
started – event signalling that a job is running Synopsis started JOB=JOB INSTANCE=INSTANCE [ENV]… Description The started event is generated by the Upstart init(8) daemon when an instance of a job has finished starting and is now running. The JOB environment variable contains the job name, and the INSTANCE environment variable contains the instance name…
stappaths – systemtap configurable file paths Description This manual page was generated on 2017-08-03 for systemtap 3.1. The following section will list the main paths in systemtap that are important to know and may be required to reference. /usr/share/systemtap/tapset/ The directory for the standard probe-alias / function tapset library, unless overridden by the SYSTEMTAP_TAPSET environment…
spufs – SPU filesystem Description The SPU filesystem is used on PowerPC machines that implement the Cell Broadband Engine Architecture in order to access Synergistic Processor Units (SPUs). The filesystem provides a name space similar to POSIX shared memory or message queues. Users that have write permissions on the filesystem can use spu_create(2) to establish…
SoX – Sound eXchange, the Swiss Army knife of audio manipulation Description This manual describes SoX supported file formats and audio device types; the SoX manual set starts with sox(1). Format types that can SoX can determine by a filename extension are listed with their names preceded by a dot. Format types that are optionally…
socket – Linux socket interface Synopsis #include <sys/socket.h> sockfd = socket(int socket_family, int socket_type, int protocol); Description This manual page describes the Linux networking socket layer user interface. The BSD compatible sockets are the uniform interface between the user process and the network protocol stacks in the kernel. The protocol modules are grouped into protocol…
socket – event signalling that a socket connection has been made Synopsis socket PROTO=PROTO PORT=PORT ADDR=ADDR socket PROTO=PROTO SOCKET_PATH=PATH Description The socket event is generated by the upstart-socket-bridge(8) daemon when a socket connection is made whose details match the socket event condition and environment specified in a jobs start on or stop on stanza. When…
sock_diag – obtaining information about sockets Synopsis #include <linux/inet_diag.h> /* for IPv4 and IPv6 sockets */ #include <linux/sock_diag.h> #include <linux/unix_diag.h> /* for UNIX domain sockets */ #include <sys/socket.h> diag_socket = socket(AF_NETLINK, socket_type, NETLINK_SOCK_DIAG); Description The sock_diag netlink subsystem provides a mechanism for obtaining information about sockets of various address families from the kernel. This subsystem…
smokeping_upgrade – Notes on upgrading Smokeping Overview This document tries to list incompatible or otherwise user-visible changes in Smokeping versions, with instructions on how to fix any possible problems. It also sporadically mentions new features and the like. The document currently starts with changes from 1.34 to 1.37. If you run into problems with upgrading…
smokeping_master_slave – How to run multiple distributed instances of SmokePing Overview Normally smokeping probes run their tests from the host where smokeping runs to some target host and monitor the latency of the connection between the two. The Master/Slave concept enables all smokeping probes to run remotely. The use case for this is to measure…
smokeping_install – How to install SmokePing Overview This document explains how to setup SmokePing at your site. Description Prerequisites SmokePing does not stand alone. It relies on various other tools and services being present. Apart from a Unix OS and a working Perl installation you need the following components: RRDtool 1.2.x or later Smokeping uses…
smokeping_extend – Notes on extending Smokeping Overview This document is intended to guide prospective authors in writing new Smokeping probes. It mostly describes the interface between Smokeping and its probe modules. If it seems too complicated to understand, look at the existing modules for examples. Comments and proposed changes or additions are welcome. Please send…
signal – overview of signals Description Linux supports both POSIX reliable signals (hereinafter "standard signals") and POSIX real-time signals. Signal dispositions Each signal has a current disposition, which determines how the process behaves when it is delivered the signal. The entries in the "Action" column of the table below specify the default disposition for each…
signal-safety – async-signal-safe functions Description An async-signal-safe function is one that can be safely called from within a signal handler. Many functions are not async-signal-safe. In particular, nonreentrant functions are generally unsafe to call from a signal handler. The kinds of issues that render a function unsafe can be quickly understood when one considers the…
sigevent – structure for notification from asynchronous routines Synopsis #include <signal.h> union sigval { /* Data passed with notification */ int sival_int; /* Integer value */ void *sival_ptr; /* Pointer value */ }; struct sigevent { int sigev_notify; /* Notification method */ int sigev_signo; /* Notification signal */ union sigval sigev_value; /* Data passed with…
shm_overview – overview of POSIX shared memory Description The POSIX shared memory API allows processes to communicate information by sharing a region of memory. The interfaces employed in the API are: shm_open(3) Create and open a new object, or open an existing object. This is analogous to open(2). The call returns a file descriptor for…