On 5 May 2009, at 19:29, Dennison Williams wrote: Hello all, Opening up the use of send_nsca can introduce insecurities into your system - you can do it if you can protect you server in other ways, such as allow a limited set of clients send data via nsca and encryption on the link with a common password. We use nsca to get data between the slaves and the master, so you have to be careful not to break that set up to (if you use slaves). However, this is outside of our recommended use so currently you'd be on your own doing it this way and any changes you make to code would likely be undone on the next upgrade. You could set up your own nsca daemon on a different port (perhaps using our nsca daemon binary with your own config file) so that upgrades would not affect it, but again its up to you to keep secure. Duncs -- Duncan Ferguson Senior Developer  Opsera Limited | Unit 69 Suttons Business Park Reading | Berkshire | RG6 1AZ | UK Phone: +44 (0) 845 057 7887 Mobile: +44 (0) 7968 148 748 Skype: duncan_j_ferguson Email: [email protected] www.opsera.com Opsera Limited is registered in the |
_______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/listinfo/opsview-users
