Search Results

Search found 4 results on 1 pages for 'abronte'.

Page 1/1 | 1 

• Gigabit capacity

  - by abronte

  Do gigabit ports have a total throughput of 1 gigabit so that you could be sending 800 mbit and receiving 200 mbit at the same time. Or is it 1000 in and 1000 out?

  Read the article

• Tunnel requests from remote server with ssh

  - by abronte

  I'm looking to forward requests from port 8003 on the remote machine to my localhost at port 8080

  Read the article

• Memcached broken pipe in rails

  - by abronte

  I seem to run into some random broken pipe errors if I try to access memcached a specific way. When I try to access memcached via Rails.cache, the first one or two reads/writes will result in a "MemCacheError (Broken pipe): Broken pipe" and return nil. But if I access memcached through a new object (ActiveSupport::Cache::MemCacheStore.new) I don't get the broken pipe error at all. I've tried upgrading to memcached 1.4.4 (was previously using 1.2.2) and I still got the error. I'm using rails 2.3.5. I would prefer to access memcached through Rails.cache because I takes namespaces into account. Any ideas?

  Read the article

• Broken pipe error in rails with memcached

  - by abronte

  I keep running into this error MemCacheError (Broken pipe): Broken pipe on my Rails app and I can't figure out why. When I access memcached via Rails.cache in my controller, the first 1 or 2 read/writes always seems to throw the broken pipe error. But when I access memcached by creating a new object, ActiveSupport::Cache::MemCacheStore.new, I don't seem to get this error. I also access memcached in another ruby process, and the first read always has this error regardless of the way I access memcached. I did implement a work around just by retrying the read but id rather have a better long term solution. Currently the only time I see this problem is after I restart memcached. I'm using Rails 2.3.5 and memcached 1.4.4 (I've also tried this with memcached 1.2.2).

  Read the article

1