Skip site
navigation (1)Skip section navigation (2)
FreeBSD Manual Pages
- VOP_GETEXTATTR(9)
- retrieve named extended attribute from a vnode
- VOP_LISTEXTATTR(9)
- retrieve a list of named extended attribute from a vnode
- VOP_SETEXTATTR(9)
- set named extended attribute for a vnode
- extattr(9)
- virtual file system named extended attributes
- sem_destroy(3)
- destroy an unnamed semaphore
- sem_init(3)
- initialize an unnamed semaphore
- sem_open(3), sem_close(3), sem_unlink(3)
- named semaphore operations
- c_rehash(1)
- Create symbolic links to files named by the hash values
- DOM_NamedNodeMap(3m)
- the Document Object Model (DOM) DOM_NamedNodeMap interface
- MrmFetchColorLiteral(3)
- Fetches a named color literal from a UID file "MrmFetchColorLiteral" "uil functions" "MrmFetchColorLiteral" "uid file"
- MrmFetchWidget(3)
- Fetches and creates an indexed (UIL named) application widget and its children "MrmFetchWidget" "uil functions" "MrmFetchWidget"
- MrmFetchWidgetOverride(3)
- Fetches any indexed (UIL named) application widget. It overrides the arguments specified for this application widget in UIL "MrmFetchWidgetOverride" "uil functions" "MrmFetchWidgetOverride"
- SLONIK_DEFINE(7), DEFINE(7)
- Defining a named symbol
- SoFile(3iv)
- node that reads children from a named file
- UilDumpSymbolTable(3)
- Dumps the contents of a named UIL symbol table to standard output "UilDumpSymbolTable" "uil functions" "UilDumpSymbolTable"
- UnNamedObj(3)
- 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
- XkbGetKeyboardByName(3)
- 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
- XkbGetNamedGeometry(3)
- Loads a keyboard geometry description from this database by name
- XkbGetNamedIndicator(3)
- Look up the indicator map and other information for an indicator by name
- XkbSetNamedIndicator(3)
- 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
- XmtCreateChild(3), XmtCreateChild()(3), XmtCreateQueryChild()(3), XmtCreateQueryListChild()(3)
- create a named child and all of its descendants
- XmtGetBitmap(3), XmtGetBitmap()(3), XmtGetPixmap()(3)
- find and return the named bitmap or pixmap
- XmtLoadResourceFile(3), XmtLoadResourceFile()(3), XmtLoadResourceFileList()(3)
- find named resource files and read them into the resource database
- XmtLookupPixmap(3), XmtLookupPixmap()(3), XmtLookupSimplePixmap()(3), XmtLookupWidgetPixmap()(3), XmtLookupBitmap()(3), XmtLookupBitmask()(3)
- get a named pixmap or bitmap from the Xmt image cache
- XmtSetValue(3), XmtSetValue()(3), XmtSetTypedValue()(3)
- set a named widget resource to a named value
- c_rehash(1), rehash(1)
- Create symbolic links to files named by the hash values
- cronolog(1m)
- write log messages to log files named according to a template
- dblink_cancel_query(3)
- cancels any active query on the named connection
- dblink_error_message(3)
- gets last error message on the named connection
- dblink_get_connections(3)
- returns the names of all open named dblink connections
- dns-boot-check(1)
- check /etc/named.boot file "dns-boot-check(1)" "check /etc/named.boot file"
- dns-conf-check(1)
- check /etc/named.conf file "dns-conf-check(1)" "check /etc/named.conf file"
- gcloud_compute_instance-groups_get-named-ports(1), gcloud compute instance-groups get-named-ports(1)
- lists the named ports for an instance group resource
- gcloud_compute_instance-groups_managed_get-named-ports(1), gcloud compute instance-groups managed get-named-ports(1)
- lists the named ports for a managed instance group
- gcloud_compute_instance-groups_managed_set-named-ports(1), gcloud compute instance-groups managed set-named-ports(1)
- sets the list of named ports for an instance group
- gcloud_compute_instance-groups_set-named-ports(1), gcloud compute instance-groups set-named-ports(1)
- sets the list of named ports for an instance group
- gcloud_compute_instance-groups_unmanaged_get-named-ports(1), gcloud compute instance-groups unmanaged get-named-ports(1)
- lists the named ports for an instance group resource
- gcloud_compute_instance-groups_unmanaged_set-named-ports(1), gcloud compute instance-groups unmanaged set-named-ports(1)
- sets the list of named ports for an instance group
- gcloud_config_configurations(1), gcloud config configurations(1)
- manage the set of gcloud named configurations
- gcloud_config_configurations_activate(1), gcloud config configurations activate(1)
- activates an existing named configuration
- gcloud_config_configurations_create(1), gcloud config configurations create(1)
- creates a new named configuration
- gcloud_config_configurations_delete(1), gcloud config configurations delete(1)
- deletes a named configuration
- gcloud_config_configurations_describe(1), gcloud config configurations describe(1)
- describes a named configuration by listing its properties
- gcloud_config_configurations_list(1), gcloud config configurations list(1)
- lists available named configurations
- gcloud_topic_configurations(1), gcloud topic configurations(1)
- supplementary help for named configurations
- getmail_maildir(1)
- read a message from stdin and deliver to a named maildir
- getmail_mbox(1)
- read a message from stdin and deliver to a named mboxrd-format mbox file with fcntl-style locking
- git-archive(1)
- 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)
- gnutls_x509_trust_list_add_named_crt(3)
- API function
- gnutls_x509_trust_list_verify_named_crt(3)
- 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
- idnconv(1)
- codeset converter for named.conf and zone master files
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- named(8)
- Internet domain name server
- named-checkconf(8)
- named configuration file syntax checking tool
- named-checkzone(8), named-compilezone(8)
- zone file validity checking or converting tool
- named-journalprint(8)
- print zone journal in human-readable form
- named-rrchecker(1)
- syntax checker for individual DNS resource records
- named.conf(5)
- configuration file for named
- ocf_heartbeat_named(7)
- Manages a named server
- panda_getfontobj(3)
- 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
- pfsinmulti(1)
- read several streams of frames and write pfs streams to named pipes
- pvm_gsize(3)
- Returns the number of members presently in the named group
- pvm_joingroup(3)
- Enrolls the calling process in a named group
- pvm_lvgroup(3)
- Unenrolls the calling process from a named group
- registrar(1)
- registrar has been renamed to rspregistrar in rsplib-3.0.0!
- server(1)
- 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(1)
- terminal has been renamed to rspterminal in rsplib-3.0.0!
- unibi_from_term(3)
- read a terminfo entry for a named terminal
- xwit(1)
- window interface tool: pop or iconify this xterm window or named windows
- AI::Categorizer::Category(3)
- A named category of documents
- Bio::Map::GeneRelative(3)
- Represents being relative to named sub-regions of a gene
- Class::Accessor::Named(3)
- Better profiling output for Class::Accessor
- Class::NamedParms(3)
- A lightweight base class for checked get/set property accessors
- Class::ParmList(3)
- Methods for processing named parameter lists
- Color::Library(3)
- An easy-to-use and comprehensive named-color library
- Color::Palette(3)
- a set of named colors
- Config::MVP::Sequence(3)
- 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
- DBIx::Class::Migration::Script::Help::delete_named_sets(3)
- Delete dumped fixture sets
- DBIx::Class::Migration::Script::Help::dump_named_sets(3)
- Dump specified fixture sets
- Data::Localize::Format::NamedArgs(3)
- Process Lexicons With Named Args (As Opposed To Positional Args)
- Data::Validator::Role::SmartSequenced(3)
- Deals with sequenced and named parameters
- DateTime::Event::NameDay(3)
- Perl DateTime extension to work with namedays from various countries
- Devel::Constants(3)
- translates constants back to named symbols
- Encode::JP::Emoji::Property(3)
- Emoji named character properties
- FEAR::API::Filters(3)
- 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
- Gantry::Conf::FAQ(3)
- 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: $ script.pl --instance=app1-dev instead of: $ script.pl --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
- Getargs::Long(3)
- Named subroutine arguments, with optional type checking
- Lingua::EN::NamedEntity(3)
- Basic Named Entity Extraction algorithm
- MathML::Entities(3)
- Convert XHTML+MathML Named Entities to Numeric Character References
- NetAddr::IP::Count(3)
- Count hosts in named subnets
- Opcode(3)
- Disable named opcodes when compiling perl code
- PDF::API2::NamedDestination(3)
- Add named destination shortcuts to a PDF
- PPIx::Regexp::Structure::NamedCapture(3)
- Represent a named capture
- PPIx::Regexp::Token::GroupType::NamedCapture(3)
- Represent a named capture
- Perl::Critic::Policy::RegularExpressions::ProhibitEnumeratedClasses(3)
- Use named character classes instead of explicit character lists
- Rose::HTML::Object::Errors(3)
- Error ids and named constants for use with HTML objects
- Rose::HTML::Object::Messages(3)
- Message ids and named constants for use with HTML objects
- SVK::Editor::Rename(3)
- An editor that translates editor calls for renamed entries
- Tie::Hash::NamedCapture(3)
- Named regexp capture buffers
- Toader::Page(3)
- This provides methods for a named page
- URI::FromHash(3)
- Build a URI from a set of named parameters
- Ubic::Multiservice(3)
- interface of multiservice representing several named services
- VCP::RefCountedFile(3)
- An object that deletes a named file when nothing refers to it any more
- XML::DOM::NamedNodeMap(3)
- A hash table interface for XML::DOM
- XML::GDOME::NamedNodeMap(3), XML::GDOME::NamedNodeMap(3)
- Interface NamedNodeMap implementation
- all_sf(nged)
- 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
- charnames(3)
- access to Unicode character names and named character sequences; also define character names
- i(nged)
- Adds obj_name to the end of the combination named comb_name. The operation may be +, -, or u.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- opentemp(3)
- create and open a uniquely-named file
- pg(3)
- Distributed, Named Process Groups
- pg2(3)
- Distributed Named Process Groups
- redraw_vlist(nged)
- 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
- shapefact(1)
- obtain shape factors between named regions of mged database
- tstatd(1)
- 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 '127.0.0.1:3638'. "--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'
- vdraw(nged)
- 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
