I think if anything, enable by default and publish in the docs how to disable if desired.tmcdonald wrote:This would need to be discussed. I'm somewhat on the fence as to whether this should be default, though I do lean slight to the "yes" side. I could see cases where someone would not want disks to fill up because they have network issues all the time, or they have restrictions on saving this sort of thing, but those would not be the majority.
NRDS "buffer" to send results once connection restored
Re: NRDS "buffer" to send results once connection restored
Re: NRDS "buffer" to send results once connection restored
That is a good idea about the documentation.
Did you try the fix and did it work for you?
Did you try the fix and did it work for you?
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: NRDS "buffer" to send results once connection restored
I'm going to suggest it goes the other direction, disabled by default, but options to turn it on..derekb wrote:I think if anything, enable by default and publish in the docs how to disable if desired.tmcdonald wrote:This would need to be discussed. I'm somewhat on the fence as to whether this should be default, though I do lean slight to the "yes" side. I could see cases where someone would not want disks to fill up because they have network issues all the time, or they have restrictions on saving this sort of thing, but those would not be the majority.
Here's my reasoning behind this.. NRDS get installed on clients, and in theory, with a mis-configuration you could fill a client disk with the generated XML, causing catastrophe. Therefore, you should have to deliberately turn the feature on.