Separate NAG from Web Interface

Daniel Wittenberg daniel-wittenberg at uiowa.edu
Wed May 14 21:40:14 CEST 2003


Unless you could write something that watches the status.log in
real-time and sends everything over a socket to the other machine... ?

Dan

On Wed, 2003-05-14 at 14:31, Jason Lancaster wrote:
> Any solution you might be able to devise would take away from the speed that
> the status.log is updated therefore, I would urge you to run httpd on the
> server that runs nagios.
> 
> If you didn't mind delayed statistics/updates in general and a lot of hard
> work, you could create a duplicate copy of the status.log and anything else
> needed every minute or so and copy it over to the server running the web
> interface, then copy any commands made on the web interface back using a
> modified form of nsca or something.
> 
> I really wouldn't recommend. From what I know, Nagios is meant to be run on
> the system that also runs the webserver.
> 
> -Jason
> 



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null





More information about the Users mailing list