PATHVERIFY(3)PATHVERIFY(3)NAME
pathverify - stand alone RFC3280 path validation and discovery tool.
SYNOPSIS
pathverify [options] files...
DESCRIPTION
pathverify is for validating the configuration of pathfinderd, as well as providing a simple, command line program to verify X.509 certifi-
cates.
OPTIONS
pathverify supports the following options:
-c, --config=ini:filename.ini
Config moniker (default: ini:/etc/pathfinderd.ini)
-p, --policy=POLICY
Initial policy set to use for validation, in tcl-encoded form (default: 2.5.29.32.0)
-q, --quiet
Decrease log level (can be used multiple times)
--skip-crl-check
Skips any CRL checking.
-t, --type=TYPE
Certificate type: der or pem (default: pem)
-v, --verbose
Increase log level (can be used multiple times)
--usage
Give a short usage message
-?, --help
Show summary of options.
SEE ALSO pathclient(3), pathfinderd(8).
AUTHOR
pathfinder was written by Carillon Information Security Inc.
This manual page was written by Patrick Patterson <ppatters@debian.org>, for the Debian project (but may be used by others).
December 23, 2007 PATHVERIFY(3)
Check Out this Related Man Page
Nagios::Plugin::Config(3pm) User Contributed Perl Documentation Nagios::Plugin::Config(3pm)NAME
Nagios::Plugin::Config - read nagios plugin .ini style config files
SYNOPSIS
# Read given nagios plugin config file
$Config = Nagios::Plugin::Config->read( '/etc/nagios/plugins.ini' );
# Search for and read default nagios plugin config file
$Config = Nagios::Plugin::Config->read();
# Access sections and properties (returns scalars or arrayrefs)
$rootproperty = $Config->{_}->{rootproperty};
$one = $Config->{section}->{one};
$Foo = $Config->{section}->{Foo};
DESCRIPTION
Nagios::Plugin::Config is a subclass of the excellent Config::Tiny, with the following changes:
o Repeated keys are allowed within sections, returning lists instead of scalars
o Write functionality has been removed i.e. access is read only
o Nagios::Plugin::Config searches for a default nagios plugins file if no explicit filename is given to "read()". The current standard
locations checked are:
/etc/nagios/plugins.ini
/usr/local/nagios/etc/plugins.ini
/usr/local/etc/nagios /etc/opt/nagios/plugins.ini
/etc/nagios-plugins.ini
/usr/local/etc/nagios-plugins.ini
/etc/opt/nagios-plugins.ini
To use a custom location, set a "NAGIOS_CONFIG_PATH" environment variable to the set of directories that should be checked. The first
"plugins.ini" or "nagios-plugins.ini" file found will be used.
SEE ALSO
Config::Tiny, Nagios::Plugin
AUTHORS
This code is maintained by the Nagios Plugin Development Team: <http://nagiosplug.sourceforge.net>.
COPYRIGHT and LICENCE
Copyright (C) 2006-2007 by Nagios Plugin Development Team
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.14.2 2010-12-03 Nagios::Plugin::Config(3pm)
I use a file's Infocentre.exe . In the infocentre's log, i can see "Can't find data for requested period" for a lot of machine . How have I a good parameter in infocentre.ini to have not this message ?
Cordialement in french for futur response . (1 Reply)
I need to run a process a large number of times.
In /home/runx, I have process X, which accesses a file X.ini.
X.ini contains 3 variables, as follows :
X_date=ccccmm
X_location=aaa
X_type= t
where date will be 200501 thru 200611
location will be aaa, bbb, ccc, or ddd
type ... (2 Replies)
Hi,
I need to perform some validation steps on the files before I start loading them.
1. I need to check for the availabilty of the file in expected path with expected name.
2. I need to check If the file format is correct.
a. confirm if correct delimiter is used.
b.... (1 Reply)
Hello.
I am trying to modify a config file which is in windows *.ini type file.
I have found a piece of code here :linux - Edit file in unix using SED - Stack Overflow
As I can't make it doing the job , I am trying to find a solution step by step.
here a modified sample file : my_sample.ini... (1 Reply)