search for: bufffers

Displaying 5 results from an estimated 5 matches for "bufffers".

Did you mean: buffers
2007 Sep 28
2
OpenSSL bufffer overflow
I did not see any commits to the OpenSSL code, recently; is anybody going to commit the fix? See http://www.securityfocus.com/archive/1/480855/30/0 for details ... Regards, STefan
2004 Sep 16
1
IAX2 only asterisk scalability
Would anybody have any numbers on how large a box would be required to convert 100 or 200 SIP calls to IAX2, without transcoding, echo cancel, .. Or a setup with individual IAX2 calls coming on one side, and trunking being used to 1 or more remote boxes on the other side, to improve bandwidth usage ? It doesn't matter if you don't have a test done for exactly 100 or 200 calls, I'm
2002 Jan 07
3
ESS with Xemacs? [vs. Emacs, slightly off topic]
...quire the mouse. Then myfile.R has something I can re-run (about 1/10 the size of .Rhistory). It seems that you can't do this in Xemacs. In particular, the kill buffer is not common to the various Xemacs processes that are running, unlike Emacs. I tried running the R process and myfile.R as bufffers in one Xemacs process, and this worked OK until I also tried help. Then I had three buffers, and it took many many keystrokes to switch from one to the other. I know that some people really like Xemacs with R. Can you give any advice? In the meantime I've gone back to Emacs. Sigh. Jon Bar...
2003 May 31
3
why are these files being transfered
Setup: Redhat linux 7.3 rrsync: version 2.5.6 protocol version 27 I'm trying to employ rsync in conjuction with with a cvs setup. The setup employs a bufffer where changes are made then moved to a checked out module from cvs repository and finally any cvs actions necessary are done. So far just testing this out with some copies of both directory trees. Right now the files in both are
2014 Nov 21
3
Second copy engine on GF116
On Fri, Nov 21, 2014 at 1:16 AM, Andy Ritger <aritger at nvidia.com> wrote: > Hi Ilia, > > Actually 0x90b8 is different than copy engine. I'm not very familiar > with it, but 0x90b8 is an engine for performing LZO decompression as > part of performing the copy. It has a variety of limitations (e.g., > cannot handle blocklinear format), and was only in a few Fermi