CPANPLUS::Hacking (3p) - developing in the CPANPLUS environment
Env (3p) - perl module that imports environment variables as scalars or arrays
adjtime (2) - correct the time to allow synchronization of the system clock
an (4) - Aironet Communications 4500/4800 IEEE 802.11FH/b wireless network device
attroff, wattroff, attron, wattron, attrset, wattrset, color_set, wcolor_set, standend, wstandend, standout, wstandout, attr_get, wattr_get, attr_off, wattr_off, attr_on, wattr_on, attr_set, wattr_set, chgat, wchgat, mvchgat, mvwchgat, PAIR_NUMBER (3) - curses character and window attribute control routines
axe (4) - ASIX Electronics AX88172/AX88178/AX88772 10/100/Gigabit USB Ethernet device
baudrate, erasechar, has_ic, has_il, killchar, longname, termattrs, termname (3) - curses environment query routines
cacheflush, _flush_cache (3) - CPU cache synchronization functions
corelist (1) - a commandline frontend to Module::CoreList
cron (8) - clock daemon
crontab (1) - maintain crontab files for individual users
crontab (5) - tables for driving cron
crunchgen (8) - generates build environment for a crunched binary
cy (4) - Cyclades Cyclom-{4, 8, 16}Y asynchronous comms board device driver
ecadc (4/SPARC64) - Environmental Monitoring Subsystem temperature sensor
env (1) - set and print environment
environ (4/SPARC64) - SPARC64 temperature sensor
environ (7) - user environment
evdns_init, evdns_shutdown, evdns_err_to_string, evdns_nameserver_add, evdns_count_nameservers, evdns_clear_nameservers_and_suspend, evdns_resume, evdns_nameserver_ip_add, evdns_resolve_ipv4, evdns_resolve_reverse, evdns_resolv_conf_parse, evdns_search_clear, evdns_search_add, evdns_search_ndots_set, evdns_set_log_fn (3) - asynchronous functions for DNS resolution
fsync (2) - synchronize a file's in-core state with that on disk
getenv, putenv, setenv, unsetenv (3) - environment variable functions
groff (1) - front end for the groff document formatting system
irongate (4/Alpha) - API UP1000 AMD751 Core Logic + AGP Chipset
jmb (4) - JMicron JMB36x SATA II and PATA Host Controller
jme (4) - JMicron JMC250/JMC260 10/100/Gigabit Ethernet device
jmphy (4) - JMicron JMP202/JMP211 10/100/Gigabit Ethernet PHY
lcd (4/HPPA) - front panel LCD display
lcd (4/Luna88K) - front panel LCD display
lisa (4) - STMicroelectronics LIS331DL MEMS motion sensor
msync (2) - synchronize a mapped region
pfsync (4) - packet filter state table sychronisation interface
poll (2) - synchronous I/O multiplexing
printenv (1) - print out the environment
sail (6) - multi-user wooden ships and iron men
sasyncd (8) - IPsec SA synchronization daemon for failover gateways
select (2) - synchronous I/O multiplexing
sendmail (8) - an electronic mail transport agent
sigwait (3) - synchronously accept a signal
slk_init, slk_set, slk_refresh, slk_noutrefresh, slk_label, slk_clear, slk_restore, slk_touch, slk_attron, slk_attrset, slk_attroff, slk_attr_on, slk_attr_set, slk_attr_off, slk_attr, slk_color (3) - curses soft label routines
sync (2) - synchronize disk block in-core status with that on disk
sysbutton (4/MacPPC) - Xserve G4 and G5 front system identifier button
vwaitforio (9) - wait for all outstanding asynchronous writes
window (1) - window environment
xlights (4/MacPPC) - Xserve G4 and G5 front panel LEDs
/etc/anacrontab (5) - configuration file for anacron
1) get and set methods for simple attributes can be automatically generated 2) argument lists are handled as described below 3) the protocol for object creation and initialization is close to the textbook approach generally suggested for object (3p) -oriented Perl (see below) 4) object initialization is handled correctly in the presence of multiple inheritance @AUTO_ATTRIBUTES is a list of attribute names: get and set methods are created for each attribute. By default, the name of the method is identical to the attribute (but see $CASE below). Values of attributes can be set via the new constructor, %DEFAULTS, or the set method as discussed below. @CLASS_ATTRIBUTES is a list of class attributes: get and set methods are created for each attribute. By default, the name of the method is identical to the attribute (but see $CASE below). Values of attributes can be set via the new constructor, %DEFAULTS (initialized at "declare time" (when the declare function is called) versus instance attributes, which are of course initialized at runtime), standard class variable access syntax ($PackageName::AttributeName), or the set method as discussed below. Normal inheritance rules apply to class attributes (but of course, instances of the same class share the same class variable). @OTHER_ATTRIBUTES is a list of attributes for which get and set methods are NOT generated, but whose values can be set via the new constructor or the set method as discussed below. %SYNONYMS is a hash that defines synonyms for attribues. Each entry is of the form new_attribute_name=>old_attribute_name. get and set methods are generated for the new names; these methods simply call the method for the old name. %DEFAULTS is a hash that defines default values for attributes. Each entry is of the form attribute_name=>default_value. get and set methods are generated for each attributes. $CASE controls whether additional methods are generated with all upper or all lower case names. It should be a string containing the strings upper or lower (case insenstive) if the desired case is desired. The declare function actually generates the method. This should be called once and no where else. AutoClass must be the first class in @ISA !! As usual, you create objects by calling new. Since AutoClass is the first class in @ISA, its new method is the one thats called. AutoClasss new examines the rest of @ISA and searches for a superclass that is capable of creating the object. If no such superclass is found, AutoClass creates the object itself. Once the object is created, AutoClass arranges to have all subclasses run their initialization methods (_init_self) in a top-down order. We support positional and keyword argument lists, but we strongly urge that each method pick one form or the other, as the combination is inherently ambiguous (see below).
AI::Perceptron (3p) - example of a node in a neural network.
Alternatively you can do this with the environment variable too: (3p) -
AnyEvent::AIO (3p) - truly asynchronous file and directory I/O
AnyEvent::BDB (3p) - truly asynchronous berkeley db access
AnyEvent::DBI (3p) - asynchronous DBI access
AnyEvent::DNS (3p) - fully asynchronous DNS resolution
BDB (3p) - Asynchronous Berkeley DB access
Catalyst::Plugin::ConfigLoader::Environment (3p) - Configure your application with environment variables.
Coro::AIO (3p) - truly asynchronous file and directory I/O
Coro::BDB (3p) - truly asynchronous bdb access
DBIx::Class::Manual::Troubleshooting (3p) - Got a problem? Shoot it. You're trying to make a query on a non-connected schema. Make sure you got the current resultset from $schema->resultset('Artist') on a schema object you got back from connect(). The ""DBIC_TRACE"" environment variable controls SQL tracing, so to see what is happening try
DateTime::Cron::Simple (3p) - Parse a cron entry and check against current time
EV, Event, Glib, Tk, Perl, Event::Lib, Irssi, rxvt (3p) -unicode, IO::Async, Qt and POE are various supported event loops/environments.
Event::ExecFlow::Frontend (3p) - Abstract base class for custom frontends
Finance::Quote::AEX (3p) - Obtain quotes from Amsterdam Euronext eXchange
Finch (1) - A Pimpin' Penguin console frontend to libpurple. Instant Messaging client.
HTML::Mason::CGIHandler (3p) - Use Mason in a CGI environment
HTTP::Server::Simple::CGI::Environment (3p) - a HTTP::Server::Simple mixin to provide the CGI protocol
ILAENV (3f) - called from the LAPACK routines to choose problem-dependent parameters for the local environment
IO::AIO (3p) - Asynchronous Input/Output
Log::Log4perl::Appender::Synchronized (3p) - Synchronizing other appenders
Mail::Mailer (3p) - Simple interface to electronic mailing mechanisms
Mail::Send (3p) - Simple electronic mail interface
Mail::SpamAssassin::AsyncLoop (3p) - scanner asynchronous event loop
Siege (7) - was designed orignally as a internet usage simulator. In short, its role was to simulate the activity of many simultaneous users hitting a HTTP server. We were debugging some java code and during that process we arrived at a point where the code could withstand an acceptable number of users hitting a single URL but it could not withstand the seemingly random activity that characterizes many users hitting many URLs on a webserver. In order to debug the problem in a lab environment, I developed a program that simply read a bunch of URLs ( we used images, scripts, static html, jsps, etc. ) into memory and hit them randomly. The result was a success. We were able to break the code in the lab, an occurance which ultimately allowed us to fix it and put it into production. As the developers code improved, siege improved until we ultimately had good java code and a pretty decent regression tool. It was helpful for us, I hope it is helpful to you. In order to feel comfortable putting code into production, you need a way to measure its performance and to determine its threshold for failure. If you break your database pool at 250 simultaneous users and you average less then one-hundred simultaneous users and the code performs favorably, you can feel good about putting it into production. At the same time, if you should monitor trends in your site's activity and prepare for the moment when your traffic starts to near your threshold for failure. As a webdeveloper or websystems administrator you have little to no control over your user group. They can visit your site anytime day or night. Your domain name could resemble a popular site, yoohoo.com? And when was the last time marketing informed you about an approaching advertising blitz? You must be prepared for anything. That is why stress and performance testing is so importantwould not recommend putting anything into production until you have a good feel for how it will perform under duress.
Sybase::BCP (3p) - Simple front end to the Sybase BCP API
Sybase::BLK (3p) - Simple front end to the Sybase Bulk Libraries (from ctlib/comlib)
TSTIEE (3f) - called from the LAPACK routines to choose problem-dependent parameters for the local environment
Template (3p) - Front-end module to the Template Toolkit
The (3) - basic structure of an mp4 file is that the file is a container for one or more tracks. These tracks contain one type of media, such as audio or video. Each track has its own timeline, samples, and properties. An example of a sample is a frame of video. The file describes how to synchronize the timelines of the tracks and the aggregate properties of the tracks.
XML::Sablotron (3p) - a Perl interface to the Sablotron XSLT processor
XML::Sablotron::DOM (3p) - The DOM interface to Sablotron's internal structures
XML::Sablotron::DOM::DOMHandler (3p) - A Perl extention of the XML::Sablotron::DOM class, that implements the sablotron DOMHandler callback functions.
XML::Sablotron::SAXBuilder (3p) - builds a Sablotron DOM document from SAX events
XML::Sablotron::Situation::DOMHandlerDispatcher (3p) - Perl sample implementation of the Sablotron DOMHandler callback interface
XmComboBoxUpdate (3) - A ComboBox function that resynchronizes data
XmRedisplayWidget (3) - Synchronously activates the expose method of a widget to draw its content
XmStringCreateSimple (3) - A compound string function that creates a compound string in the language environment of a widget
anacron (8) - runs commands periodically
cc (1) - front-end to the C compiler
cronolog (1m) - write log messages to log files named according to a template
cronosplit (1m) - split log files into cronolog-compatible files
curl_getenv (3) - return value for environment name
cvsync (1) - synchronize CVS repositories
cvsyncd (1) - synchronize CVS repositories
envdir (8) - runs another program with environment modified according to files in a specified directory.
envsubst (1) - substitutes environment variables in shell format strings
envuidgid (8) - runs another program with environment variables indicating a specified account's uid and gid.
evince (1) - GNOME document viewer The Evince Document Viewer application for GNOME desktop environment
git-rev-list (1) - Lists commit objects in reverse chronological order
growisofs (1) - combined mkisofs frontend/DVD recording program.
install-mh (1) - initialize the nmh environment
ldap.conf, .ldaprc (5) - LDAP configuration file/environment variables
libssh2_channel_setenv_ex (3) - set an environment variable on the channel
llvm-g++ (1) - LLVM C++ front-end
llvm-gcc (1) - LLVM C front-end
mkocp (1) - frontend to otp2ocp(1)
mkofm (1) - front end to mktextfm(1)
prompter (1) - prompting editor front-end for nmh
rcvdist (1) - asynchronously redistribute new mail
rcvstore (1) - asynchronously incorporate mail into a folder
sabcmd (1) - a command line interface to Sablotron XSLT processor
slocal (1) - asynchronously filter and deliver new mail
spamassassin (1) - simple front-end filtering script for SpamAssassin
spamassassin (3p) - simple front-end filtering script for SpamAssassin
svnsync (1) - Subversion repository synchronization tool
synctex (1/\") - command line client tool to support the Synchronize TeXnology available in recent TeX engines.
synctex (5) - Synchronize TeXnology help file
texexec (1) - front end to the ConTeXt typesetting system
whatnow (1) - prompting front-end for sending messages
xcdroast (1) - graphical frontend to create or copy CDs.
zenmap (1) - Graphical Nmap frontend and results viewer
zshzftpsys (1) - zftp function front-end
XSynchronize, XSetAfterFunction (3) - enable or disable synchronization
XdbeSwapBuffers (3) - swaps front and back DBE buffers.
citron (4) - Citron Infrared Touch Driver (CiTouch)
glCullFace (3G) - specify whether frontor back-facing facets can be culled
glFrontFace (3G) - define frontand back-facing polygons
glGetTexEnvfv, glGetTexEnviv (3G) - return texture environment parameters
glTexEnvf, glTexEnvi, glTexEnvfv, glTexEnviv (3G) - set texture environment parameters
glXSwapBuffers (3) - exchange front and back buffers
ico (1) - animate an icosahedron or other polyhedron
koi8rxterm (1) - X terminal emulator for KOI8-R environments
tek4957 (4) - Tektronix 4957 input driver
uxterm (1) - X terminal emulator for Unicode (UTF-8) environments