Hi.
We need to distribute a couple of extra libraries as part of the nrpd installation.
I can see two approaches.
1) hook into the process that builds the installnrds script and add our stuff to that
2) create a similar process that acts as a post-install procedure.
Does option 1 or 2 seem like the better alternative?
I've pored through a bunch of the php code that is involved in building and shipping the installnsrds script and, while I'm getting warmer, it's still a lot of code to parse.
I'm hoping someone here can make this a little easier for me.
I've been trying to understand how the wget command works for this install:
wget -O linux.tar.gz "http://123.45.67.89/[b]nrdp[/b]/?cmd=nrdsgetclient&token=46703duu3ps2&configname=linux"
There is no nrpd subdirectory under the DocumentRoot /var/www/html. Looking at httpd.conf, I see no alias for nrpd.
I likely will not have access to httpd.conf in production (to create my own alias for my code/data repository) so would like to piggyback on the installnrds process as much as possible.
I hope this question makes sense.
Thanks very much, as always.
Rick
post install for nrdp agent
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: post install for nrdp agent
If you are needing to include plugins in NRDS I would suggest you check out this
http://library.nagios.com/library/produ ... s-tutorial
Specifically the document on page 3 explains how to add custom plugins
http://library.nagios.com/library/produ ... s-tutorial
Specifically the document on page 3 explains how to add custom plugins