| /dports/net-mgmt/p5-Net-NSCA-Client/Net-NSCA-Client-0.009002/ |
| H A D | META.yml | 22 name: Net-NSCA-Client
29 Net::NSCA::Client:
30 file: lib/Net/NSCA/Client.pm
32 Net::NSCA::Client::Connection:
35 Net::NSCA::Client::Connection::TLS:
38 Net::NSCA::Client::DataPacket:
41 Net::NSCA::Client::InitialPacket:
44 Net::NSCA::Client::Library:
47 Net::NSCA::Client::ServerConfig:
50 Net::NSCA::Client::Utils:
[all …]
|
| H A D | MANIFEST | 3 lib/Net/NSCA/Client.pm
4 lib/Net/NSCA/Client/Connection.pm
5 lib/Net/NSCA/Client/Connection/TLS.pm
6 lib/Net/NSCA/Client/DataPacket.pm
7 lib/Net/NSCA/Client/InitialPacket.pm
8 lib/Net/NSCA/Client/Library.pm
9 lib/Net/NSCA/Client/ServerConfig.pm
10 lib/Net/NSCA/Client/Troubleshooting.pod
11 lib/Net/NSCA/Client/Utils.pm
21 t/tests/MyTest/Net/NSCA/Client.pm
[all …]
|
| H A D | SIGNATURE | 24 SHA1 8029b3cc8e61c11074e14b7107564311e13ce75a lib/Net/NSCA/Client.pm
25 SHA1 8bcfd32c5d953e4fb884835b2a6a46cb58e0840d lib/Net/NSCA/Client/Connection.pm
26 SHA1 b788771cf65638e5065bf47bb9519eb7a32b67b9 lib/Net/NSCA/Client/Connection/TLS.pm
27 SHA1 344b8cc57d92d13b2746b0ad7fc75db13a86d3bd lib/Net/NSCA/Client/DataPacket.pm
28 SHA1 b822a4a897cc8e2e25541e089aeabff7e1904a9e lib/Net/NSCA/Client/InitialPacket.pm
29 SHA1 e21d75cd25cc6ddd56c7a38e005893472764efcb lib/Net/NSCA/Client/Library.pm
30 SHA1 9f839cf570d2b2423e5ba19824e83ee008a255e4 lib/Net/NSCA/Client/ServerConfig.pm
31 SHA1 c14222122c1df3eb538fbc64a4c604b6711a855d lib/Net/NSCA/Client/Troubleshooting.pod
32 SHA1 14730c6e211fdb318506d6aef69a15414eb42698 lib/Net/NSCA/Client/Utils.pm
37 SHA1 6e94cf782c305b07587d9238d0624f23c5c60ac3 t/tests/MyTest/Net/NSCA/Client.pm
[all …]
|
| H A D | Changes | 1 Revision history for Perl 5 distribution Net-NSCA-Client
38 - Allow communicating with NSCA servers that have been custom-compiled
42 standard NSCA client/server does.
69 that comes with the NSCA package.
79 Net::NSCA::Client::InitialPacket.
82 - The initialization_vector attribute in Net::NSCA::Client::InitialPacket
87 - Creating a Net::NSCA::Client::InitialPacket without an IV would cause an
91 - Added SEE ALSO section in Net::NSCA::Client.
92 - Fixed documentation in Net::NSCA::Client::DataPacket to specify all
|
| H A D | README | 1 Net-NSCA-Client 0.009002
26 perldoc Net::NSCA::Client
30 * [RT, CPAN's request tracker](http://rt.cpan.org/NoAuth/Bugs.html?Dist=Net-NSCA-Client)
32 * [CPAN Ratings](http://cpanratings.perl.org/d/Net-NSCA-Client)
34 * [Search CPAN](http://search.cpan.org/dist/Net-NSCA-Client)
|
| /dports/net-mgmt/p5-Net-NSCA-Client/Net-NSCA-Client-0.009002/t/ |
| H A D | live_server.t | 11 use Net::NSCA::Client ();
12 use Net::NSCA::Client::Connection::TLS ();
13 use Net::NSCA::Client::InitialPacket ();
23 my $client = Net::NSCA::Client->new(
34 status => $Net::NSCA::Client::STATUS_OK,
93 status => $Net::NSCA::Client::STATUS_OK,
150 my $client = Net::NSCA::Client->new(%args,
187 my $client = Net::NSCA::Client->new(%args);
235 my $client = Net::NSCA::Client->new(%args,
262 my $client = Net::NSCA::Client->new(%args);
[all …]
|
| /dports/net-mgmt/nsca-ng/nsca-ng-1.6/ |
| H A D | README.md | 1 Welcome to NSCA-ng!
4 The NSCA-ng package provides a client-server pair which makes the "Nagios
9 NSCA-ng supports TLS encryption and shared-secret authentication with
27 order to embed a private copy of libConfuse into NSCA-ng, the
33 libev is embedded into NSCA-ng, so this dependency is optional.
44 NSCA-ng's source directory should do the trick:
64 Don't build and install the NSCA-ng client.
88 NSCA-ng. In order to force usage of the included copy,
114 this package) could be used to start and stop the NSCA-ng server.
122 NSCA Compatibility
[all …]
|
| H A D | README | 1 Welcome to NSCA-ng!
4 The NSCA-ng package provides a client-server pair which makes the "Nagios
9 NSCA-ng supports TLS encryption and shared-secret authentication with
27 order to embed a private copy of libConfuse into NSCA-ng, the
33 libev is embedded into NSCA-ng, so this dependency is optional.
44 NSCA-ng's source directory should do the trick:
64 Don't build and install the NSCA-ng client.
88 NSCA-ng. In order to force usage of the included copy,
114 this package) could be used to start and stop the NSCA-ng server.
122 NSCA Compatibility
[all …]
|
| /dports/net-mgmt/nsca-ng-client/nsca-ng-1.6/ |
| H A D | README.md | 1 Welcome to NSCA-ng!
4 The NSCA-ng package provides a client-server pair which makes the "Nagios
9 NSCA-ng supports TLS encryption and shared-secret authentication with
27 order to embed a private copy of libConfuse into NSCA-ng, the
33 libev is embedded into NSCA-ng, so this dependency is optional.
44 NSCA-ng's source directory should do the trick:
64 Don't build and install the NSCA-ng client.
88 NSCA-ng. In order to force usage of the included copy,
114 this package) could be used to start and stop the NSCA-ng server.
122 NSCA Compatibility
[all …]
|
| H A D | README | 1 Welcome to NSCA-ng!
4 The NSCA-ng package provides a client-server pair which makes the "Nagios
9 NSCA-ng supports TLS encryption and shared-secret authentication with
27 order to embed a private copy of libConfuse into NSCA-ng, the
33 libev is embedded into NSCA-ng, so this dependency is optional.
44 NSCA-ng's source directory should do the trick:
64 Don't build and install the NSCA-ng client.
88 NSCA-ng. In order to force usage of the included copy,
114 this package) could be used to start and stop the NSCA-ng server.
122 NSCA Compatibility
[all …]
|
| H A D | PROTOCOL | 1 The NSCA-ng Protocol, Version 1
7 This is an informal description of the NSCA-ng Protocol, Version 1, used for
8 transmitting "monitoring commands" from NSCA-ng clients to NSCA-ng servers.
17 The NSCA-ng server listens on TCP port 5668. As soon as an NSCA-ng client
25 first NSCA-ng request. All NSCA-ng data MUST be transmitted as TLS
28 NSCA-ng Session
44 An NSCA-ng session is a sequence of one or more request-response pairs and
84 If a `MOIN` request is sent, it MUST be the first request of an NSCA-ng
101 If a `PING` request is sent, it MUST be the first request of an NSCA-ng
131 `PUSH` request. The client MAY issue multiple `PUSH` requests per NSCA-ng
[all …]
|
| /dports/net-mgmt/p5-Net-NSCA-Client/Net-NSCA-Client-0.009002/lib/Net/NSCA/ |
| H A D | Client.pm | 1 package Net::NSCA::Client;
19 use Net::NSCA::Client::Library 0.009 qw(Bytes Hostname PortNumber Timeout);
24 use Net::NSCA::Client::Connection;
25 use Net::NSCA::Client::Connection::TLS;
26 use Net::NSCA::Client::DataPacket;
27 use Net::NSCA::Client::ServerConfig ();
75 default => sub { Net::NSCA::Client::ServerConfig->new },
109 my $tls = Net::NSCA::Client::Connection::TLS->new(@tls_args);
116 my $connection = Net::NSCA::Client::Connection->new(@connection_args);
119 my $data_packet = Net::NSCA::Client::DataPacket->new(
|
| /dports/net-mgmt/p5-Net-NSCA-Client/Net-NSCA-Client-0.009002/lib/Net/NSCA/Client/ |
| H A D | Troubleshooting.pod | 3 Net::NSCA::Client::Troubleshooting - Troubleshooting information
9 When a packet is sent to the NSCA server and the following errror appears
14 This can be cause by a number of reasons, as NSCA provides this as a
30 =head3 NSCA server compiled using custom constants
32 It is possible that the NSCA server was compiled with the constants
34 NSCA, you will need to setup the client to use the same constant values.
35 See L<Net::NSCA::Client::ServerConfig|Net::NSCA::Client::ServerConfig> on
42 this would occur is if the NSCA's data packet constants where changed and
43 the client needs L<Net::NSCA::Client::ServerConfig|Net::NSCA::Client::ServerConfig>
54 The time stamp that is sent with the data packet is checked on the NSCA
|
| H A D | Connection.pm | 1 package Net::NSCA::Client::Connection;
19 use Net::NSCA::Client::Library qw(Hostname PortNumber Timeout);
26 use Net::NSCA::Client::InitialPacket;
27 use Net::NSCA::Client::ServerConfig ();
64 default => sub { Net::NSCA::Client::ServerConfig->new },
160 my $initial_packet = Net::NSCA::Client::InitialPacket->new(
|
| H A D | InitialPacket.pm | 1 package Net::NSCA::Client::InitialPacket;
19 use Net::NSCA::Client::Library 0.009 qw(Bytes);
24 use Net::NSCA::Client::ServerConfig ();
25 use Net::NSCA::Client::Utils qw(initialize_moose_attr_early);
58 default => sub { Net::NSCA::Client::ServerConfig->new },
|
| /dports/net-mgmt/nsca27-client/nsca-2.7.2/sample-config/ |
| H A D | nsca.cfg.in | 2 # Sample NSCA Daemon Config File
10 # The name of the file in which the NSCA daemon should write it's process ID
11 # number. The file is only written if the NSCA daemon is started by the root
27 # Address that NSCA has to bind to in case there are
28 # more as one interface and we do not want NSCA to bind
35 # NSCA USER
36 # This determines the effective user that the NSCA daemon should run as.
39 # NOTE: This option is ignored if NSCA is running under either inetd or xinetd
45 # NSCA GROUP
46 # This determines the effective group that the NSCA daemon should run as.
[all …]
|
| /dports/net-mgmt/nsca27/nsca-2.7.2/nsca_tests/ |
| H A D | nsca_basic.cfg | 2 # Sample NSCA Daemon Config File
10 # The name of the file in which the NSCA daemon should write it's process ID
11 # number. The file is only written if the NSCA daemon is started by the root
27 # Address that NSCA has to bind to in case there are
28 # more as one interface and we do not want NSCA to bind
35 # NSCA USER
36 # This determines the effective user that the NSCA daemon should run as.
39 # NOTE: This option is ignored if NSCA is running under either inetd or xinetd
45 # NSCA GROUP
46 # This determines the effective group that the NSCA daemon should run as.
[all …]
|
| /dports/net-mgmt/nsca27/nsca-2.7.2/sample-config/ |
| H A D | nsca.cfg.in | 2 # Sample NSCA Daemon Config File
10 # The name of the file in which the NSCA daemon should write it's process ID
11 # number. The file is only written if the NSCA daemon is started by the root
27 # Address that NSCA has to bind to in case there are
28 # more as one interface and we do not want NSCA to bind
35 # NSCA USER
36 # This determines the effective user that the NSCA daemon should run as.
39 # NOTE: This option is ignored if NSCA is running under either inetd or xinetd
45 # NSCA GROUP
46 # This determines the effective group that the NSCA daemon should run as.
[all …]
|
| /dports/net-mgmt/nsca27-client/nsca-2.7.2/nsca_tests/ |
| H A D | nsca_basic.cfg | 2 # Sample NSCA Daemon Config File
10 # The name of the file in which the NSCA daemon should write it's process ID
11 # number. The file is only written if the NSCA daemon is started by the root
27 # Address that NSCA has to bind to in case there are
28 # more as one interface and we do not want NSCA to bind
35 # NSCA USER
36 # This determines the effective user that the NSCA daemon should run as.
39 # NOTE: This option is ignored if NSCA is running under either inetd or xinetd
45 # NSCA GROUP
46 # This determines the effective group that the NSCA daemon should run as.
[all …]
|
| /dports/net-mgmt/nsca-client/nsca-2.9.2/nsca_tests/ |
| H A D | nsca_basic.cfg | 2 # Sample NSCA Daemon Config File
10 # The name of the file in which the NSCA daemon should write it's process ID
11 # number. The file is only written if the NSCA daemon is started by the root
27 # Address that NSCA has to bind to in case there are
28 # more as one interface and we do not want NSCA to bind
35 # NSCA USER
36 # This determines the effective user that the NSCA daemon should run as.
39 # NOTE: This option is ignored if NSCA is running under either inetd or xinetd
45 # NSCA GROUP
46 # This determines the effective group that the NSCA daemon should run as.
[all …]
|
| /dports/net-mgmt/nsca/nsca-2.9.2/nsca_tests/ |
| H A D | nsca_basic.cfg | 2 # Sample NSCA Daemon Config File
10 # The name of the file in which the NSCA daemon should write it's process ID
11 # number. The file is only written if the NSCA daemon is started by the root
27 # Address that NSCA has to bind to in case there are
28 # more as one interface and we do not want NSCA to bind
35 # NSCA USER
36 # This determines the effective user that the NSCA daemon should run as.
39 # NOTE: This option is ignored if NSCA is running under either inetd or xinetd
45 # NSCA GROUP
46 # This determines the effective group that the NSCA daemon should run as.
[all …]
|
| /dports/net-mgmt/nsca27/nsca-2.7.2/ |
| H A D | SECURITY | 2 NSCA SECURITY README
8 Before you proceed with installing the NSCA daemon daemon on your
13 users could potentionally use the NSCA client to send fake service
14 and host check results to the NSCA daemon (and thus Nagios). This
42 to the NSCA daemon.
67 2) The NSCA client stuff the check results into a packet (or
70 3) The NSCA client computes the CRC-32 value of the packet
83 5) The NSCA daemon recieves the packet and decrypts it using
136 NSCA daemon receives is "valid" data - i.e., it was
142 To help prevent this, the NSCA daemon generates what is
[all …]
|
| /dports/net-mgmt/nsca/nsca-2.9.2/ |
| H A D | SECURITY | 2 NSCA SECURITY README
8 Before you proceed with installing the NSCA daemon daemon on your
13 users could potentionally use the NSCA client to send fake service
14 and host check results to the NSCA daemon (and thus Nagios). This
42 to the NSCA daemon.
67 2) The NSCA client stuff the check results into a packet (or
70 3) The NSCA client computes the CRC-32 value of the packet
83 5) The NSCA daemon recieves the packet and decrypts it using
136 NSCA daemon receives is "valid" data - i.e., it was
142 To help prevent this, the NSCA daemon generates what is
[all …]
|
| /dports/net-mgmt/nsca27-client/nsca-2.7.2/ |
| H A D | SECURITY | 2 NSCA SECURITY README
8 Before you proceed with installing the NSCA daemon daemon on your
13 users could potentionally use the NSCA client to send fake service
14 and host check results to the NSCA daemon (and thus Nagios). This
42 to the NSCA daemon.
67 2) The NSCA client stuff the check results into a packet (or
70 3) The NSCA client computes the CRC-32 value of the packet
83 5) The NSCA daemon recieves the packet and decrypts it using
136 NSCA daemon receives is "valid" data - i.e., it was
142 To help prevent this, the NSCA daemon generates what is
[all …]
|
| /dports/net-mgmt/nsca-client/nsca-2.9.2/ |
| H A D | SECURITY | 2 NSCA SECURITY README
8 Before you proceed with installing the NSCA daemon daemon on your
13 users could potentionally use the NSCA client to send fake service
14 and host check results to the NSCA daemon (and thus Nagios). This
42 to the NSCA daemon.
67 2) The NSCA client stuff the check results into a packet (or
70 3) The NSCA client computes the CRC-32 value of the packet
83 5) The NSCA daemon recieves the packet and decrypts it using
136 NSCA daemon receives is "valid" data - i.e., it was
142 To help prevent this, the NSCA daemon generates what is
[all …]
|