weatherrc(5) [debian man page]
weatherrc(5) File Formats Manual weatherrc(5) NAME
weatherrc - configuration file format for the weather(1) utility DESCRIPTION
The weatherrc file format is intended to specify a set of aliases by which to group URIs for METAR station conditions and alert/forecast zones, but other command-line options and flags for the weather utility can be specified as well. The file is organized as an INI-format config, with the alias name in [] brackets and the associated parameter/value pairs on following lines. Parameters and their values are separated by = or : characters. Multi-word values do not need quoting. These parameters are supported... alert include local alert notices (possible values are False and True or 0 and 1) atypes list of alert notification types to display (ex: tornado_warning,urgent_weather_message) cache control all caching (possible values are False and True or 0 and 1) cache_data control retrieved data caching (possible values are False and True or 0 and 1) cache_search control search result caching (possible values are False and True or 0 and 1) cacheage duration in seconds to refresh cached data (ex: 900) cachedir directory for storing cached searches and data (ex: ~/.weather) conditions output current conditions (possible values are False and True or 0 and 1) defargs list of default command-line arguments (ex: avl,rdu) forecast include a local forecast (possible values are False and True or 0 and 1) headers list of conditions headers to display (ex: temperature,wind) imperial filter/convert conditions for US/UK units (possible values are False and True or 0 and 1) metric filter/convert conditions for metric units (possible values are False and True or 0 and 1) quiet skip preambles and don't indent (possible values are False and True or 0 and 1) setpath directory search path for correlation sets (ex: .:~/.weather) verbose show full decoded feeds (possible values are False and True or 0 and 1) EXAMPLES
The following is an example ~/.weather/weatherrc defining a couple aliases named home and work to be displayed when running the utility with no aliases specified... [default] defargs = home,work [home] description = Conditions and Forecast at Home forecast = True metar = http://weather.noaa.gov/pub/data/observations/metar/decoded/KRDU.TXT zone_forecast = http://weather.noaa.gov/pub/data/forecasts/zone/nc/ncz041.txt [work] description = Conditions at Work metar = http://weather.noaa.gov/pub/data/observations/metar/decoded/KGSO.TXT Now if weather is invoked by itself on the command line, it will output conditions for home and work, and also a forecast for home only. AUTHOR
Specification and manual written by Jeremy Stanley <fungi@yuggoth.org>. SEE ALSO
weather(1) 2.0 2012-06-24 weatherrc(5)
Check Out this Related Man Page
gss_inquire_context(3) Library Functions Manual gss_inquire_context(3) NAME
gss_inquire_context() - obtain information about a security context SYNOPSIS
DESCRIPTION
The routine provides information about the security context to the calling application. The calling application must first have called the routine for a handle for the credential. Input Parameters context_handle A handle that refers to the security context. Output Parameters src_name The name of the context initiator. If the context was established using anonymous authentication, and if the appli- cation invoking is the context acceptor, an anonymous name will be returned. Specify NULL if not required. context_handle The name of the context acceptor. If the context acceptor did not authenticate itself, and if the initiator did not specify a target name in its call to the value will be returned. Specify NULL if not required. lifetime_rec Returns the number of seconds for which the credential will remain valid. If the credential expired, the parameter returns a 0 (zero). If there is no credential expiration, the parameter returns the value If an expiration time is not required, specify NULL. targ_name The name of the context acceptor. Storage associated with this name must be freed by the application after use with a call to mech_type The security mechanism providing the context. Specify NULL if not required ctx_flags Specifies independent flags, each of which requests that the context support a service option. The following sym- bolic names are provided to correspond to each flag. The symbolic names should be logically ORed to form a bit-mask value. The True/False values are: True Credentials were delegated to the context acceptor. False No credentials were delegated. The True/False values are: True The context acceptor has been asked to authenticate itself. False The context initiator has not been asked to authenticates itself. The True/False values are: True Replayed signed or sealed messages will be detected. False Replayed messages will not be detected. The True/False values are: True Out-of-sequence signed or sealed messages will be detected. False Out-of-sequence signed or sealed messages will not be detected. The True/False values are: True Request that confidentiality service be made available False No per-message confidentiality service is required. The True/False values are: True Request that integrity service be be made available False No per-message integrity service is required. The True/False values are: True Do not reveal the initiator's identity to the acceptor. False Authenticate normally. cred_usage Returns one of the following values describing how the application can use the credential: If no usage information is required, specify NULL. mechs returns a set of security mechanisms supported by the credential. Specify NULL if not required. minor_status Returns a status code from the security mechanism. STATUS CODES
The following status codes can be returned: The routine was completed successfully. The referenced context could not be accessed. The credentials were invalid. The routine failed. Check the minor_status parameter for details. The routine could not access the credentials. AUTHOR
was developed by Sun Microsystems, Inc. SEE ALSO
gss_acquire_cred(3). The manpages for DCE-GSSAPI are included with the DCE-CoreTools product. To see those manpages add to gss_inquire_context(3)