Skip site navigation (1)Skip section navigation (2)

FreeBSD Man Pages

Man Page or Keyword Search:
Man Architecture
Apropos Keyword Search (all sections) Output format
home | help
the Document Object Model (DOM) DOM_NamedNodeMap interface
Fetches a named color literal from a UID file "MrmFetchColorLiteral" "uil functions" "MrmFetchColorLiteral" "uid file"
Fetches and creates an indexed (UIL named) application widget and its children "MrmFetchWidget" "uil functions" "MrmFetchWidget"
Fetches any indexed (UIL named) application widget. It overrides the arguments specified for this application widget in UIL "MrmFetchWidgetOverride" "uil functions" "MrmFetchWidgetOverride"
Defining a named symbol
node that reads children from a named file
Dumps the contents of a named UIL symbol table to standard output "UilDumpSymbolTable" "uil functions" "UilDumpSymbolTable"
widget from X tookit
XAllocColor(3), XAllocNamedColor(3), XAllocColorCells(3), XAllocColorPlanes(3), XFreeColors(3)
allocate and free colors
XStoreColors(3), XStoreColor(3), XStoreNamedColor(3)
set colors
XcmsAllocColor(3), XcmsAllocNamedColor(3)
allocate colors
Build a new keyboard description from a set of named components, and to optionally have the server use the resulting description to replace an active one
Loads a keyboard geometry description from this database by name
Look up the indicator map and other information for an indicator by name
Names an indicator if it is not already named; toggles the state of the indicator; sets the indicator to a specified state and sets the indicator map for the indicator
Create symbolic links to files named by the hash values
write log messages to log files named according to a template
cancels any active query on the named connection
gets last error message on the named connection
returns the names of all open named dblink connections
check /etc/named.boot file "dns-boot-check(1)" "check /etc/named.boot file"
check /etc/named.conf file "dns-conf-check(1)" "check /etc/named.conf file"
read a message from stdin and deliver to a named maildir
read a message from stdin and deliver to a named mboxrd-format mbox file with fcntl-style locking
Create an archive of files from a named tree
glBindTexture(3), "glBindTexture(3)
bind a named texture to a texturing target
glDeleteTextures(3), "glDeleteTextures(3)
delete named textures
gmkfifo(1), mkfifo(1)
make FIFOs (named pipes)
API function
API function
hdf_get_child(3), hdf_get_child (3)
return the first child of the named node
hdf_get_obj(3), hdf_get_obj (3)
return the HDF data set node at a named location
hdf_set_int_value(3), hdf_set_int_value (3)
Set the value of a named node to a number
hdf_set_value(3), hdf_set_value (3)
Set the value of a named node
hdf_set_valuef(3), hdf_set_valuef (3)
Set the value of a named node
codeset converter for named.conf and zone master files
Internet domain name server
named configuration file syntax checking tool
named-checkzone(8), named-compilezone(8)
zone file validity checking or converting tool
print zone journal in human-readable form
A syntax checker for individual DNS resource records
configuration file for named
get the object that the named font is stored in
pcre16_copy_named_substring(3), PCRE(3)
Perl-compatible regular expressions
pcre16_get_named_substring(3), PCRE(3)
Perl-compatible regular expressions
read several streams of frames and write pfs streams to named pipes
Returns the number of members presently in the named group
Enrolls the calling process in a named group
Unenrolls the calling process from a named group
registrar has been renamed to rspregistrar in rsplib-3.0.0!
server has been renamed to rspserver in rsplib-3.0.0!
smi_attribute(3), smiGetAttribute(3), smiGetFirstAttribute(3), smiGetNextAttribute(3), smiGetAttributeParentClass(3), smiGetAttributeParentType(3), smiGetFirstUniqueAttribute(3), smiGetNextUniqueAttribute(3), smiGetEvent(3), smiGetFirstEvent(3), smiGetNextEvent(3), smiGetAttributeFirstRange(3), smiGetAttributeNextRange(3), smiGetAttributeFirstNamedNumber(3), smiGetAttributeNextNamedNumber(3)
SMI Attribute information routines
smi_type(3), smiGetType(3), smiGetFirstType(3), smiGetNextType(3), smiGetParentType(3), smiGetTypeLine(3), smiGetFirstRange(3), smiGetNextRange(3), smiGetFirstNamedNumber(3), smiGetNextNamedNumber(3), smiGetTypeModule(3)
SMI type information routines
terminal has been renamed to rspterminal in rsplib-3.0.0!
Logs real-time accounting daemon SYNOPSIS tstatd [ options ] plugin [zone1:]wildcard1 .. [zoneN:]wildcardN OPTIONS "-a zone, --agregate-zone=zone" 4 Item "-a zone, --agregate-zone=zone" Agregate data from all anonymous logs (wildcards without explicit zone specified) into zone. Default behavior is to create new zone for each anonymous log from its file name. "-b file, --database-file=file" 4 Item "-b file, --database-file=file" Use file as persistent storage to keep accumulated data across daemon restarts. Default is auto generated from daemon name, specified identity and '.db' suffix. "--basename" 4 Item "--basename" Use only base name (excluding directories and suffix) of anonymous log file for auto-created zones. "-c dir, --change-dir=dir" 4 Item "-c dir, --change-dir=dir" Change current directory to dir before wildcards expanding. "-d, --debug" 4 Item "-d, --debug" Composition of options: --foreground and --log-level=debug. "-f, --foreground" 4 Item "-f, --foreground" Don't detach daemon from control terminal, logging to stderr instead log file or syslog. "--log-facility=name" 4 Item "--log-facility=name" Use name as facility for syslog logging (see syslog (3) for list of available values). Default is 'daemon'. "--log-level=level" 4 Item "--log-level=level" Set minimal logging level to level (see syslog (3) for list of available values). Default is 'notice'. "--log-file=file" 4 Item "--log-file=file" Use logging to file instead of syslog logging (which is default). "-e num, --expand-period=num" 4 Item "-e num, --expand-period=num" Do wildcards re-expanding and checking for new and missed logs every num seconds. Default is '60'. "-h, --help" 4 Item "-h, --help" Print brief help message about available options. "-i string, --identity=string" 4 Item "-i string, --identity=string" Just a string used in title of daemon process, syslog ident (see syslog|(3)), --database-file and --pid-file. Idea behind this options - multiple tstatd instances running simultaneosly. "-l [address:]port, --listen=[address:]port" 4 Item "-l [address:]port, --listen=[address:]port" Specify address and port for TCP listen socket binding. Default is ''. "--multiple" 4 Item "--multiple" With this option specified same log file could be included into several zones (if log name satisifies several wildcards). Default behavior is to include log file only in first satisified zone. "-n num, --windows-num=num" 4 Item "-n num, --windows-num=num" Set number of sliding-windows to num. Default is '60'. "-o string, --options=string" 4 Item "-o string, --options=string" Comma-separated plugin supported options (like a mount (8) options). "--override-from=file" 4 Item "--override-from=file" Load content of file into plugin package namespace. This is way to easy customize plugin behavior without creating another plugin. "-p file, --pid-file=file" 4 Item "-p file, --pid-file=file" Use file to keep daemon process id. Default is auto generated from daemon name, specified identity and '.pid' suffix. "--parse-error=level" 4 Item "--parse-error=level" Do logging with level (see syslog (3) for available values) about all unparsed log lines. Hint: use 'none' for ignoring such lines. Default is defining by plugin and usually is 'debug'. "-r pattern, --regex=pattern" 4 Item "-r pattern, --regex=pattern" Use pattern instead of plugin default regular expression for matching log lines. "--regex-from=file" 4 Item "--regex-from=file" Load regular expression from file and use instead of plugin default regular expression for matching log lines. "-s num, --store-period=num" 4 Item "-s num, --store-period=num" Store accumulated data in a persistent storage every num seconds. Default is '60'. "--timer=zone:timer:num" 4 Item "--timer=zone:timer:num" Create named timer firing every num seconds for zone. "-u <user>, --user=user" 4 Item "-u <user>, --user=user" Change effective privileges of daemon process to user. "-v, --version" 4 Item "-v, --version" Print version information of tstatd and exit. "-w num, --window-size=<num>" 4 Item "-w num, --window-size=<num>" Set size (duration) of sliding window to num seconds. Default is '10'
window interface tool: pop or iconify this xterm window or named windows
A named category of documents
Represents being relative to named sub-regions of a gene
Better profiling output for Class::Accessor
A lightweight base class for checked get/set property accessors
Methods for processing named parameter lists
An easy-to-use and comprehensive named-color library
a set of named colors
an ordered set of named configuration sections
Convert::Color(3), "Convert::Color"(3)
color space conversions and named lookups
Convert::Color::VGA(3), "Convert::Color::VGA"(3)
named lookup for the basic VGA colors
Convert::Color::X11(3), "Convert::Color::X11"(3)
named lookup of colors from X11's rgb.txt
Delete dumped fixture sets
Dump specified fixture sets
Process Lexicons With Named Args (As Opposed To Positional Args)
Deals with sequenced and named parameters
Perl DateTime extension to work with namedays from various countries
translates constants back to named symbols
Emoji named character properties
Named filters
Future::Phrasebook(3), "Future::Phrasebook"(3)
coding examples for "Future" and "Future::Utils" This documentation-only module provides a phrasebook-like approach to giving examples on how to use Future and Future::Utils to structure Future-driven asynchronous or concurrent logic. As with any inter-dialect phrasebook it is structured into pairs of examples; each given first in a traditional call/return Perl style, and second in a style using Futures. In each case, the generic function or functions in the example are named in "ALL_CAPITALS()" to make them stand out. In the examples showing use of Futures, any function that is expected to return a "Future" instance is named with a leading "F_" prefix. Each example is also constructed so as to yield an overall future in a variable called "$f", which represents the entire operation
Frequently Asked Questions regarding Gantry::Conf "Why should I use Gantry::Conf at all?" 4 Item "Why should I use Gantry::Conf at all?" There are many reasons why we feel Gantry::Conf is helpful both during development and after deployment. The next two entries should hopefully answer this question for you as they outline a few common scenarios programmers and system administrators often face. "How is Gantry::Conf helpful during development?" 4 Item "How is Gantry::Conf helpful during development?" "Easy separation of development configs from production configs" 4 Item "Easy separation of development configs from production configs" Often programmers have a separate development environment from their production environment. By using <shared> blocks and dev instances you can avoid spending any serious time setting up your application in the development environment. Take this configuration example: <shared dev> dbuser nobody dbpass secret dbconn "dbi:Pg:dbname=dev" </shared> <shared production> dbuser apache dbpass secret2 dbconn "dbi:Pg:dbname=production" </shared> <instance app1> ConfigureVia FlatFile Config::General /etc/apps/app1.conf use production </instance> <instance app1-dev> ConfigureVia FlatFile Config::General /etc/apps/app1.conf use dev </instance> By separating out our production and dev database information into shared blocks we can essentially switch between our production and dev environments by simply changing the instance we are using. If you were working on a script this would be a simple matter of running: $ --instance=app1-dev instead of: $ --instance=app1 "How is Gatnry::Conf helpful in production?" 4 Item "How is Gatnry::Conf helpful in production?" Gantry::Conf has several advantages in a production environment. First, it provides a single place for all config information, if you commit to it. Even if you don't commit to it for all apps, it still provides control to the installing admin over how and where conf information is stored. For instance, the admin could put the config information directly into /etc/gantry.conf, or into a separate file in /etc/gantry.d. She could even set up a secure web server where all boxes would go to get their conf. The short answer is, Gantry::Conf is flexible and production environments benefit from flexibility. "How do I pass my instance information into my application?" 4 Item "How do I pass my instance information into my application?" There are many possible ways to do this a few of which are: "Command line arguments" 4 Item "Command line arguments" If your application accepts arguments on the command line we suggest adding an --instance option to pass in the instance's name. "PerlSetVar" 4 Item "PerlSetVar" In a mod_perl environment you could use a PerlSetVar, possibly named GantryConfInstance, to pull in this value for your application. "ModPerl::ParamBuilder" 4 Item "ModPerl::ParamBuilder" Again in a mod_perl environment, another option would be to use ModPerl::ParamBuilder to pass the instance name. "Hard coded" 4 Item "Hard coded" We include this for the sake of completeness, but advise against it. You could always simply hard code your instance information into your application, but this will greatly reduce the flexibility you have. "How do I add a different provider for an existing ConfigVia method?" 4 Item "How do I add a different provider for an existing ConfigVia method?" Place your provider module in the Gantry::Conf::Provider::Method::* namespace. Make sure your public API matches the existing providers which use the same method. For instance the flat file providers all implement a config method which is called as a class method and receives a file name. "How do I add to the ConfigVia methods?" 4 Item "How do I add to the ConfigVia methods?" If none of the existing provider methods will do, you need to work in Gantry::Conf. In particular, you need to augment the dispatch hash with the name of your provisioning method and a sub name which will handle it. Then you need to implement the method you put in %dispatch
Named subroutine arguments, with optional type checking
Basic Named Entity Extraction algorithm
Convert XHTML+MathML Named Entities to Numeric Character References
Count hosts in named subnets
Disable named opcodes when compiling perl code
Add named destination shortcuts to a PDF
Represent a named capture
Represent a named capture
Use named character classes instead of explicit character lists
Error ids and named constants for use with HTML objects
Message ids and named constants for use with HTML objects
An editor that translates editor calls for renamed entries
Named regexp capture buffers
This provides methods for a named page
Build a URI from a set of named parameters
interface of multiservice representing several named services
An object that deletes a named file when nothing refers to it any more
A hash table interface for XML::DOM
XML::GDOME::NamedNodeMap(3), XML::GDOME::NamedNodeMap(3)
Interface NamedNodeMap implementation
obtain shape factors between named regions of an entire mged database
allocimage(3), allocimagemix(3), freeimage(3), nameimage(3), namedimage(3), setalpha(3), loadimage(3), cloadimage(3), unloadimage(3), readimage(3), writeimage(3), bytesperline(3), wordsperline(3)
allocating, freeing, reading, writing images
access to Unicode character names and named character sequences; also define character names
Adds obj_name to the end of the combination named comb_name. The operation may be “+,” “-,” or “u.”
create and open a uniquely-named file
Distributed, Named Process Groups
Distributed Named Process Groups
Given the name(s) of database objects, regenerate the vlist associated with every shape in view that references the named object(s), either shapes or regions
searchpath(3), search(3)
search for named executable
obtain shape factors between named regions of mged database
read a terminfo entry for a named terminal
Allows drawing of lines and polygons (optionally with per vertex normals) in the MGED graphics display. It is used to build a named list of drawing commands for MGED, send the list to the MGED display, modify the list, or delete all or part of the list
home | help