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

FreeBSD Manual Pages

  
 
  

home | help
extattr_namespace_to_string(3), extattr_string_to_namespace(3)
convert an extended attribute namespace identifier to a string and vice versa
sysdecode_enum(3), sysdecode_acltype(3), sysdecode_atfd(3), sysdecode_extattrnamespace(3), sysdecode_fadvice(3), sysdecode_fcntl_cmd(3), sysdecode_getfsstat_mode(3), sysdecode_getrusage_who(3), sysdecode_idtype(3), sysdecode_ipproto(3), sysdecode_kldsym_cmd(3), sysdecode_kldunload_flags(3), sysdecode_lio_listio_mode(3), sysdecode_madvice(3), sysdecode_minherit_flags(3), sysdecode_msgctl_cmd(3), sysdecode_nfssvc_flags(3), sysdecode_pathconf_name(3), sysdecode_prio_which(3), sysdecode_procctl_cmd(3), sysdecode_ptrace_request(3), sysdecode_rlimit(3), sysdecode_rtprio_function(3), sysdecode_scheduler_policy(3), sysdecode_sctp_pr_policy(3), sysdecode_sctp_sinfo_flags(3), sysdecode_semctl_cmd(3), sysdecode_shmctl_cmd(3), sysdecode_shutdown_how(3), sysdecode_sigbus_code(3), sysdecode_sigchld_code(3), sysdecode_sigfpe_code(3), sysdecode_sigill_code(3), sysdecode_signal(3), sysdecode_sigprocmask_how(3), sysdecode_sigsegv_code(3), sysdecode_sigtrap_code(3), sysdecode_sockaddr_family(3), sysdecode_socketdomain(3), sysdecode_sockettype(3), sysdecode_sockopt_level(3), sysdecode_sysarch_number(3), sysdecode_umtx_op(3), sysdecode_vmresult(3), sysdecode_whence(3)
lookup name of various enumerated values
Itcl_Class(3), Itcl_CreateClass(3), Itcl_DeleteClass(3), Itcl_FindClass(3), Itcl_IsClass(3), Itcl_IsClassNamespace(3)
Manipulate classes
SDLmm(3)
The namespace for the SDLmm library
SPI_getnspname(3)
return the namespace of the specified relation
Tcl_AppendExportList.tcl85(3), Tcl_AppendExportList(3), Tcl_CreateNamespace(3), Tcl_DeleteNamespace(3), Tcl_Export(3), Tcl_FindCommand(3), Tcl_FindNamespace(3), Tcl_ForgetImport(3), Tcl_GetCurrentNamespace(3), Tcl_GetGlobalNamespace(3), Tcl_GetNamespaceUnknownHandler(3), Tcl_Import(3), Tcl_SetNamespaceUnknownHandler(3)
manipulate namespaces
Tcl_AppendExportList.tcl86(3), Tcl_AppendExportList(3), Tcl_CreateNamespace(3), Tcl_DeleteNamespace(3), Tcl_Export(3), Tcl_FindCommand(3), Tcl_FindNamespace(3), Tcl_ForgetImport(3), Tcl_GetCurrentNamespace(3), Tcl_GetGlobalNamespace(3), Tcl_GetNamespaceUnknownHandler(3), Tcl_Import(3), Tcl_SetNamespaceUnknownHandler(3)
manipulate namespaces
Tcl_AppendExportList.tcl87(3), Tcl_AppendExportList(3), Tcl_CreateNamespace(3), Tcl_DeleteNamespace(3), Tcl_Export(3), Tcl_FindCommand(3), Tcl_FindNamespace(3), Tcl_ForgetImport(3), Tcl_GetCurrentNamespace(3), Tcl_GetGlobalNamespace(3), Tcl_GetNamespaceUnknownHandler(3), Tcl_Import(3), Tcl_SetNamespaceUnknownHandler(3)
manipulate namespaces
Tcl_ClassGetMetadata.tcl86(3), Tcl_ClassGetMetadata(3), Tcl_ClassSetMetadata(3), Tcl_CopyObjectInstance(3), Tcl_GetClassAsObject(3), Tcl_GetObjectAsClass(3), Tcl_GetObjectCommand(3), Tcl_GetObjectFromObj(3), Tcl_GetObjectName(3), Tcl_GetObjectNamespace(3), Tcl_NewObjectInstance(3), Tcl_ObjectDeleted(3), Tcl_ObjectGetMetadata(3), Tcl_ObjectGetMethodNameMapper(3), Tcl_ObjectSetMetadata(3), Tcl_ObjectSetMethodNameMapper(3)
manipulate objects and classes
Tcl_ClassGetMetadata.tcl87(3), Tcl_ClassGetMetadata(3), Tcl_ClassSetMetadata(3), Tcl_CopyObjectInstance(3), Tcl_GetClassAsObject(3), Tcl_GetObjectAsClass(3), Tcl_GetObjectCommand(3), Tcl_GetObjectFromObj(3), Tcl_GetObjectName(3), Tcl_GetObjectNamespace(3), Tcl_NewObjectInstance(3), Tcl_ObjectDeleted(3), Tcl_ObjectGetMetadata(3), Tcl_ObjectGetMethodNameMapper(3), Tcl_ObjectSetMetadata(3), Tcl_ObjectSetMethodNameMapper(3)
manipulate objects and classes
Tcl_CreateEnsemble.tcl85(3), Tcl_CreateEnsemble(3), Tcl_FindEnsemble(3), Tcl_GetEnsembleFlags(3), Tcl_GetEnsembleMappingDict(3), Tcl_GetEnsembleNamespace(3), Tcl_GetEnsembleUnknownHandler(3), Tcl_GetEnsembleSubcommandList(3), Tcl_IsEnsemble(3), Tcl_SetEnsembleFlags(3), Tcl_SetEnsembleMappingDict(3), Tcl_SetEnsembleSubcommandList(3), Tcl_SetEnsembleUnknownHandler(3)
manipulate ensemble commands
Tcl_CreateEnsemble.tcl86(3), Tcl_CreateEnsemble(3), Tcl_FindEnsemble(3), Tcl_GetEnsembleFlags(3), Tcl_GetEnsembleMappingDict(3), Tcl_GetEnsembleNamespace(3), Tcl_GetEnsembleParameterList(3), Tcl_GetEnsembleUnknownHandler(3), Tcl_GetEnsembleSubcommandList(3), Tcl_IsEnsemble(3), Tcl_SetEnsembleFlags(3), Tcl_SetEnsembleMappingDict(3), Tcl_SetEnsembleParameterList(3), Tcl_SetEnsembleSubcommandList(3), Tcl_SetEnsembleUnknownHandler(3)
manipulate ensemble commands
Tcl_CreateEnsemble.tcl87(3), Tcl_CreateEnsemble(3), Tcl_FindEnsemble(3), Tcl_GetEnsembleFlags(3), Tcl_GetEnsembleMappingDict(3), Tcl_GetEnsembleNamespace(3), Tcl_GetEnsembleParameterList(3), Tcl_GetEnsembleUnknownHandler(3), Tcl_GetEnsembleSubcommandList(3), Tcl_IsEnsemble(3), Tcl_SetEnsembleFlags(3), Tcl_SetEnsembleMappingDict(3), Tcl_SetEnsembleParameterList(3), Tcl_SetEnsembleSubcommandList(3), Tcl_SetEnsembleUnknownHandler(3)
manipulate ensemble commands
code(i4), itcl::code(i4)
capture the namespace context for a code fragment
code(itcl)
capture the namespace context for a code fragment
getdns_context_set_append_name(3)
getdns_context_set_context_update_callback, getdns_context_set_dns_root_servers, getdns_context_set_dns_transport, getdns_context_set_dnssec_trust_anchors, getdns_context_set_dnssec_allowed_skew, getdns_context_set_follow_redirects, getdns_context_set_limit_outstanding_queries, getdns_context_set_namespaces, getdns_context_set_resolution_type, getdns_context_set_suffix, getdns_context_set_timeout, -- getdns context manipulation routines n
gitnamespaces(7)
Git namespaces
hxunxmlns(1)
replace XML "global names" by Namespace prefixes
hxxmlns(1)
replace XML Namespace prefixes by "global names"
namespace.tcl85(n), namespace(n)
create and manipulate contexts for commands and variables
namespace.tcl86(n), namespace(n)
create and manipulate contexts for commands and variables
namespace.tcl87(n), namespace(n)
create and manipulate contexts for commands and variables
scope(i4), itcl::scope(i4)
capture the namespace context for a variable
scope(itcl)
capture the namespace context for a variable
variable.tcl85(n), variable(n)
create and initialize a namespace variable
variable.tcl86(n), variable(n)
create and initialize a namespace variable
variable.tcl87(n), variable(n)
create and initialize a namespace variable
AnyEvent::XMPP::Namespaces(3)
XMPP namespace collection and aliasing class
CHI::Stats(3)
Record and report per-namespace cache statistics
CORE(3)
Namespace for Perl's core routines
Class::Forward(3)
Namespace Dispatch and Resolution
DBIx::Class::Helper::ResultSet::VirtualView(3)
Clean up your SQL namespace (DEPRECATED)
DBIx::Class::Helper::VirtualView(3)
(DEPRECATED) Clean up your SQL namespace
DBIx::Class::Migration::Script::Help::schema_class(3)
The namespace of your Schema
Data::Localize::Namespace(3)
Acquire Lexicons From Module %Lexicon Hash
Data::Object::Space(3)
Namespace Class
Devel::Caller::IgnoreNamespaces(3)
make available a magic caller() which can ignore namespaces that you tell it about
Devel::InheritNamespace(3)
Inherit An Entire Namespace
Devel::REPL::Plugin::CompletionDriver::Globals(3)
Complete global variables, packages, namespaced functions
ExportTo(3)
export any function/method to any namespace
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
Git::Sub(3)
git commands imported as System::Sub subs in the git:: namespace
Image::ExifTool::XMP2(3), Image::ExifTool::XMP2.pl(3)
Additional XMP namespace definitions
Internals(3)
Reserved special namespace for internals related functions
Jifty::Manual::Style(3)
Jifty coding style guide Default style Subsection "Default style" When in doubt, default to whatever Damian Conway's Perl Best Practices says. Private documentation Subsection "Private documentation" When documenting a private method, or providing documentation which is not useful to the user of the module (and is presumably useful to the developer), wrap it in =begin/end private. This way it does not show up in perldoc where a user would see it and yet is still available and well formatted (that is, not just a lump comment) when looking at the code. =begin private =head2 import_extra Called by L<Test::More>s C<import> code when L<Jifty::Test> is first C<use>d, it calls L</setup>, and asks Test::More to export its symbols to the namespace that C<use>d this one. =end private sub import_extra { ... } Test temp files Subsection "Test temp files" Files created by tests should be declared as such using Jifty::Test->test_file() so they are cleaned up on a successful test run. Use Shell::Command Subsection "Use Shell::Command" Shell::Command has a number of functions which work like common shell file commands such as touch, cp and mv. They are battle tested and cross-platform. Use them instead of coding your own. For example, instead of this: open my $file, ">foo"; close $file; Do this: use Shell::Command; touch $file; Case insensitive matching Subsection "Case insensitive matching" To check if a string equals another string case insensitively, do this lc $foo eq lc $bar; lc $foo eq bar; not this: $foo =~ /^eQ$bareE/i; $foo =~ /^bar$/i;
Lexical::Sub(3)
subroutines without namespace pollution
Lexical::Var(3)
static variables without namespace pollution
Module::Loader(3)
finding and loading modules in a given namespace
MooX::Options::Manual::NamespaceClean(3)
Use namespace::clean with MooX::Options
MooseX::Declare::Context::Namespaced(3)
Namespaced context
MooseX::Declare::Syntax::Keyword::Clean(3)
Explicit namespace cleanups
MooseX::Declare::Syntax::Keyword::Namespace(3)
Declare outer namespace
MooseX::Declare::Syntax::MooseSetup(3)
Common Moose namespaces declarations
MooseX::Declare::Syntax::NamespaceHandling(3)
Handle namespaced blocks
Net::OAI::Record::NamespaceFilter(3)
general filter class based on namespace URIs
Net::OpenID::IndirectMessage(3)
Class representing a collection of namespaced arguments
Net::XMPP2::Namespaces(3)
XMPP namespace collection and aliasing class
Net::XMPP::Namespaces(3)
In depth discussion on how namespaces are handled
OpenXPKI::Server::Workflow::Condition::DatapoolEntry(3)
n .SH "SYNOPSIS private_key_not_empty: class: OpenXPKI::Server::Workflow::Condition::DatapoolEntry param: _map_key: $cert_identifier namespace: certificate.privatekey condition: exists" .SH "SYNOPSIS private_key_not_empty: class: OpenXPKI::Server::Workflow::Condition::DatapoolEntry param: _map_key: $cert_identifier namespace: certificate.privatekey condition: exists" Header "SYNOPSIS private_key_not_empty: class: OpenXPKI::Server::Workflow::Condition::DatapoolEntry param: _map_key: $cert_identifier namespace: certificate.privatekey condition: exists"
PDL::IO(3)
An overview of the modules in the PDL::IO namespace
POE::Filter::XML::NS(3)
Provides constants that return appropriate namespace strings
Perl::Critic::Policy::Moose::RequireCleanNamespace(3)
Require removing implementation details from you packages
Plagger::Plugin::Namespace::ApplePhotocast(3)
Apple Photocast module
Plagger::Plugin::Namespace::HatenaFotolife(3)
Parses Hatena Fotolife module
Plagger::Plugin::Namespace::MediaRSS(3)
Media RSS extension
RDF::Trine::Namespace(3)
Abbreviated syntax for constructing RDF node objects
RDF::Trine::NamespaceMap(3)
Collection of Namespaces
Reflex::Eg(3)
Reflex examples namespace
Rinci::package(3)
Metadata for your namespaces/packages
Schema::Kwalify(3)
Kwalify implementation in the Schema:: namespace
Template::Namespace::Constants(3)
Compile time constant folding
Test2::Formatter(3)
Namespace for formatters
Test::CleanNamespaces(3)
Check for uncleaned imports
Variable::Eject(3)
Eject variables from hash to current namespace
WebService::GData::Constants(3)
constants (namespaces,format,services...) used for Google data APIs
XML::CommonNS(3)
A list of commonly used namespaces
XML::Compile::Schema::NameSpaces(3)
Connect name-spaces from schemas
XML::DOM2::Attribute::Namespace(3)
XML::DOM2::Attribute::Namespace
XML::DOM2::DOM::NameSpace(3)
XML::DOM2::DOM::NameSpace
XML::GDOME::XPath::Namespace(3), XML::GDOME::XPath::Namespace(3)
Interface XPathNamespace implementation
XML::LibXML::Namespace(3)
XML::LibXML Namespace Implementation
XML::Namespace(3)
Simple support for XML Namespaces
XML::NamespaceFactory(3)
Simple factory objects for SAX namespaced names
XML::NamespaceSupport(3)
A simple generic namespace processor
XML::Pastor::Schema::NamespaceInfo(3)
Class that represents the META information about a target namespace within a W3C schema
XML::RSS::LibXML::Namespaces(3)
Utility Catalog For Known Namespacee
XML::Stream::Namespace(3)
Object to make defining Namespaces easier in XML::Stream
XML::XPath::Node::Namespace(3), Namespace(3)
an XML namespace node
namespace(1)
print name space directory
namespace::autoclean(3)
Keep imports out of your namespace
namespace::clean(3)
Keep imports and functions out of your namespace
namespace::clean::xs(3)
Keep imports and functions out of your namespace, in XS
namespace::clean::xs::all(3)
Use XS for namespace::clean globally
namespace::sweep(3)
Sweep up imported subs in your classes
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'
home | help