Dave Shield wrote:
On Fri, 2005-12-02 at 17:14 +0100, Thomas Anders wrote:
Are there any drawbacks (=change in behaviour other than
bug fixing) of this approach?
OK - there's one other drawback that I've only just twigged.
The 'get_exec_output' routine directs the output from the
external command to a temporary file. This means that it
can handle arbitrary amounts of output - limited only by
the amount of disk space available!
The 'run_exec_command' uses a fixed memory buffer to hold
the output of the command - anything more than this is
simply discarded. The size of this buffer is chosen by
the calling routine, so it's reasonably flexible - but it
is a fixed buffer.
I don't know whether that would be seen as a problem or not.
Would it be better then to leave the wrapper code out for the moment and
just replace the function where you can? That would be the safest way
IMO to implement the new functionality without breaking existing code.
There may be applications out there that rely on the old caching mechanism.
Andy
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
