|
|
|
regcomp(5) -- X/Open regular expressions definition and interface
|
|
BREs Matching a Single Character or Collating Element A BRE ordinary character, a special character preceded by a backslash or a period matches a single character. A bracket expression matches a single character or a single collating element. BRE Ordinary Characters An ordinary character is a BRE t... |
|
regexp(5) -- regular expression compile and match routines
|
|
These functions are general purpose regular expression matching routines to be used in programs that perform regular expression matching. These functions are defined by the regexp.h header file. The functions step and advance do pattern matching given a character string and a compiled regular expression as input. The function compile takes as input a regular expression as defined below and produces a compiled expressio... |
|
|
replication(5) -- Memory replication
|
|
numa(5), migration(5), mtune(4), /var/sysgen/mtune/numa, refcnt(5), mmci(5), nstats(1), sn(1). PPPPaaaaggggeeee 1111 |
|
siginfo(5) -- signal generation information
|
|
If a process is catching a signal, it may request information that tells why the system generated that signal (see sigaction(2)). If a process is monitoring its children, it may receive information that tells why a child changed state (see waitid(2)). In either case, the system returns the information in a structure of type siginfo_t, which includes the following information: int si_signo /* signal number */ int si_errno /* err... |
|
signal(5) -- base signals
|
|
A signal is an asynchronous notification of an event. A signal is said to be generated for (or sent to) a process or a thread when the event associated with that signal first occurs. Examples of such events include hardware faults, timer expiration and terminal activity, as well as the invocation of the kill(2), sigqueue(3) or sigsend(2) system calls. In some circumstances, the same event generates signals for multiple processes. A process... |
|
smb.conf.5(5) -- The configuration file for the Samba suite
|
|
Each section in the configuration file (except for the [global] section) describes a shared resource (known as a "share"). The section name is the name of the shared resource and the parameters within the section define the Page 1 (printed 2/13/04) SMB.CONF(5) UNIX System V (14 March 2003) SMB.CONF(5) shares attributes. There are three special sections, [global], [homes] and [printers], which are described under special sections. The following notes apply to ordinary section descriptions. A sh... |
|
smbpasswd.5(5) -- The Samba encrypted password file
|
|
This tool is part of the Samba suite. smbpasswd is the Samba encrypted password file. It contains the username, Unix user id and the SMB hashed passwords of the user, as well as account flag information and the time the password was last changed. This file format has been evolving with Samba and has had several different formats in the past. |
|
stat(5) -- data returned by stat system call
|
|
The system calls stat, lstat and fstat return data in a stat structure, which is defined in stat.h and includes the following members: dev_t st_dev; ino_t st_ino; mode_t st_mode; nlink_t st_nlink; uid_t st_uid; gid_t st_gid; d<... |
|
stat64(5) -- data returned by stat64 system call
|
|
The system calls stat64, lstat64 and fstat64 return data in a stat64 structure, which is defined in stat.h and includes the following members: dev_t st_dev; ino64_t st_ino; mode_t st_mode; nlink_t st_nlink; uid_t st_uid; gi<... |
|
stdarg(5) -- variable argument list
|
|
This set of macros provides a means of writing portable procedures that accept variable argument lists. Routines having variable argument lists (such as printf(3)) that do not use stdarg are inherently nonportable, since different machines use different argument passing conventions. The stdarg facility is similar to varargs(5), but is based on the ANSI Standard for C. A variable argument list contains one or more parameters. The rightmost parameter plays a special role, and is designated ParmN i... |
|
term(5) -- conventional names for terminals
|
|
/usr/lib/terminfo/?/* compiled terminal description database |
|
timers(5) -- timers and process time accounting information
|
|
The timing facilities under IRIX consist of interval timers, event timing, process execution time accounting, and time of day reporting. Interval timers consist of POSIX timers (see timer_create (3c)), and itimers that were introduced in BSD4.2 (see getitimer(2)). Use of the POSIX timers is strongly recommended for new applications. The IRIXunique BSD4.2 itimers are supported only to provide compatibility for older applications. On Silicon Graphics machines there are two independent timers per p... |
|
types(5) -- primitive system data types
|
|
The data types defined in types.h are used in UNIX System code. Some data of these types are accessible to user code: typedef struct { int r[1]; } *physadr; typedef long clock_t; typedef long daddr_t; typedef long pgno_t; typedef char * addr_t; typedef char * caddr_t; typedef unsigned char unchar; typedef unsigned short ushort; typedef unsigned int uint; typedef unsigned long ulong; typedef unsigned long ino_t; typedef long uid_t; typedef long gid_t; typedef unsigned long nl... |
|
ucontext(5) -- user context
|
|
The ucontext structure defines the context of a thread of control within an executing process. This structure includes at least the following members: ucontext_t *uc_link sigset_t uc_sigmask stack_t uc_stack mcontext_t uc_mcontext uc_link is a pointer to the context that is to be resumed when this context returns. If uc_link is equal to 0, then this context is the main context, and the process exits when this context returns. The u |
|
uopt(5) -- the ucode optimizer
|
|
/usr/lib/uopt |
