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

FreeBSD Manual Pages

  
 
  

home | help
EZ_DnDGetMatchedConversionTargets(3), EZ_DnDGetMatchedConversionTargets (3)
return the lists of targets the both the drag-source and the drop-site convert
SSL_get_shared_ciphers(3)
ciphers supported by both client and server
XkbOpenDisplay(3)
Checks for a compatible version of the Xkb extension in both the library and the server, and initializes the extension for use
fid(1)
List identifiers in F1; if F2 is also given, list those common to both
hdel(1)
delete both forks of an HFS file
invert_raw_image(1)
invert 2D image along either or both axes
kakasi(1), KAKASI(1)
Kanji kana simple inverter (between Kanji, both Kana and Romaji)
mping(8)
send ICMP ECHO_REQUEST packets to multiple network hosts in a round-robbin fashion. Mping support both IPv4 and IPv6 adresses at the same time
pfsintiff(1)
Load images or frames in several variants of TIFF format (both LDR and HDR)
radsecproxy(1)
a generic RADIUS proxy that provides both RADIUS UDP and TCP/TLS (RadSec) transport
sc_SpatialMOPairIter_eq(3), sc::SpatialMOPairIter_eq(3)
SpatialMOPairIter_eq gives the ordering of same-spin and different-spin orbital pairs if both orbitals of the pairs are from the same space
Bio::Graphics::Glyph::dumbbell(3)
A glyph that draws a "dumbbell" with the same shapes on both ends
Bio::TreeIO::NewickParser(3), Module(3)
which implements a newick string parser as a finite state machine which enables it to parse the full Newick specification. Taken largely from the Ensembl Compara file with the same name (Bio::EnsEMBL::Compara::Graph::NewickParser), this module adapts the parser to work with BioPerl's event handler-based parsing scheme. This module is used by nhx.pm and newick.pm, and is NOT called directly. Instead, both of those parsing modules extend this module in order to gain access to the main parsing method
DBIx::Admin::DSNManager(3)
Manage a file of DSNs, for both testing and production
Data::Dumper(3)
stringified perl data structures, suitable for both printing and "eval"
FileHandle::Fmode(3)
determine whether a filehandle is opened for reading, writing, or both
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
Getopt::Compact(3)
getopt processing in a compact statement with both long and short options, and usage functionality
IO::Socket::IP(3), "IO::Socket::IP"(3)
Family-neutral IP socket supporting both IPv4 and IPv6
IO::Socket::Socks(3)
Provides a way to create socks client or server both 4 and 5 version
IPC::Open2(3)
open a process for both reading and writing using open2()
MPI_Win_flush(3), MPI_Win_flush_all(3)
Complete all outstanding RMA operations at both the origin and the target
MPI_Win_flush_local(3), MPI_Win_flush_local_all(3)
Complete all outstanding RMA operations at both the origin
Math::GSL::Heapsort(3)
Functions for sorting data, both directly and indirectly (using an index)
Module::Load(3)
runtime require of both modules and files
Monitoring::Plugin::ExitResult(3)
Helper class for returning both output and return codes when testing
MooseX::AttributeShortcuts::Trait::Attribute::HasAnonBuilder(3)
Attributes, etc, common to both the role-attribute and attribute traits
Nagios::Plugin::ExitResult(3)
Helper class for returning both output and return codes when testing
Net::EPP::Protocol(3)
Low-level functions useful for both EPP clients and servers
Net::FreshBooks::API::Role::Common(3)
Roles common to both Base.pm and API.pm
OpenXPKI::Server::Workflow::Condition::KeyGenerationMode(3)
Check if the profile allows key generation as specified by the "generate" parameter. Example: can_use_server_key: class: OpenXPKI::Server::Workflow::Condition::KeyGenerationMode param: generate: server _map_profile: $cert_profile Returns true if the key generation setting is either escrow, server or both. The setting is obtained for the given profile (by profile or from the default setting) from the node key.generate. If this node is missing, client is allowed and server is assumed ok if key.alg is not empty. If the profile parameter is not given in the configuration, the context value of cert_profile is used
PerlX::Maybe(3)
return a pair only if they are both defined
Perlanet(3)
A program for creating programs that aggregate web feeds (both RSS and Atom)
Test::Assertions(3)
a simple set of building blocks for both unit and runtime testing
Time::ParseDate(3)
-- date parsing both relative and absolute
po4a(1p)
update both the PO files and translated documents in one shot
pods::SDL::Cookbook::PDL(3), SDL::CookBook::PDL(3)
-- CookBook for SDL + PDL PDL provides great number crunching capabilities to Perl and SDL provides game-developer quality real-time bitmapping and sound. You can use PDL and SDL ''together'' to create real-time, responsive animations and simulations. In this section we will go through the pleasures and pitfalls of working with both powerhouse libraries
put_comb(nged)
Insert combinations and regions - allows definition of both boolean expressions and standard attribute values
translate(nged)
Used to precisely control the translation of an object in both primitive edit and matrix edit modes
xmerl_xs(3)
Erlang has similarities to XSLT since both languages have a functional programming approach
home | help