More like use a fricking passphrase at least to protect your private key and use some kind of agent to save you from typing that passphrase again and again.
I sometimes use passphraseless private key when I control where it is stored but never store a passphraseless private key on line.
Be aware of key loggers and other means to get you passphrase once your private key is stored online also.
hmmm... Linus sounds right to me too. He specifically said, or almost, that people wanting to load 10 pages in sandboxed firefox process/thread in parallel could find a use for 16 cores;-)
gee, as a kid, I spent countless hours there. I usually ended up buying more reliable brands in more distant stores but they got some of my money for sure.
It apparently is indeed. I always suspected that this was due to the simplicity of English and my belief that you can write it "almost" properly with little knowledge of grammar and analysis. In contrast, to write in French "almost" properly, it's hard to get away without knowing those rules. When used to grammar and analysis, the "it's vs its" dilemma becomes easy to solve.
I have seem at least 10 benchmarks showing the same. Do your own research and try to be a little less biased. Latest apache does the same as nginx now. Event driven model with multiple connections handled by a single thread. That is as simple as that and it shouldn't be too hard to understand that using the same techniques, apache will indeed be as fast.
> both in ease of administration and more importantly, in performance (why is Apache still spawning processes for every request that comes in..
Apache has had thread model (no need to fork new processes) and EVEN nginx like event model, with fewer/threads than connections for quite a while. Update your info. We run latest IIS and apache on production servers and IIS seems to do pretty well but saying the things you say about apache isn't fair and false in some cases.
In fact, we run instances of apache with event model (max 75 threads, max 4096 connections, keep alive 5 seconds) as a caching reverse proxy and WAF (mod_security) in front of IIS application servers and others. Centralized WAF configuration for all applications and caching so all static content requests rarely hit the application servers.
App server behind the caching reverse-proxy get 2 to 15 work threads, keepalive rarely on, the config is fine tuned with the help of benchmarks and yes, some backend apps are faster with only 2 workers and often degrade with more than 15.
Slashdot Mirror
Vas chier mon tabernacle! Attends que te case le geule en 2!
English is doing fine. I don't see it fading away so quickly.
Cardassian of course
https://en.wikipedia.org/wiki/...
https://en.wikipedia.org/wiki/...
You almost spelled Rivest right:
https://en.wikipedia.org/wiki/...
Keep on the good work!
Just fucking use PKI instead of stupid API keys. Are their API keys PKI or not. See my post above:
http://slashdot.org/comments.p...
then, since 1977:
https://en.wikipedia.org/wiki/...
.bash_history eavesdropping is indeed kidiporn...
Run a WAF, log suspicious packets at the IP level, then you will discover a big underworld...
More like use a fricking passphrase at least to protect your private key and use some kind of agent to save you from typing that passphrase again and again.
I sometimes use passphraseless private key when I control where it is stored but never store a passphraseless private key on line.
Be aware of key loggers and other means to get you passphrase once your private key is stored online also.
Wait! Should I understand they aren't using PKA?
Sorry then, shame on me.
Nope, I only say that because I already thought the same way before I was aware of his view. It happens all the time.
hmmm... Linus sounds right to me too. He specifically said, or almost, that people wanting to load 10 pages in sandboxed firefox process/thread in parallel could find a use for 16 cores ;-)
is your recommendation valid for RAID 1 as well? I am just curious...
-Thanks,
> Even my home file server uses two tiny second gen 64gb SSDs for read/write caching for ~20TB of data.
Did you configure this manually or just used something off the shelf? What is setup to accomplish this?
-Thanks,
Great, except I live in Australia.
Exactly, think of the children !
My name is John Kodak you insensitive clod.
https://www.facebook.com/john....
gee, as a kid, I spent countless hours there. I usually ended up buying more reliable brands in more distant stores but they got some of my money for sure.
agreed, same opinion here, a lot of it was crap but some was relatively OK.
It apparently is indeed. I always suspected that this was due to the simplicity of English and my belief that you can write it "almost" properly with little knowledge of grammar and analysis. In contrast, to write in French "almost" properly, it's hard to get away without knowing those rules. When used to grammar and analysis, the "it's vs its" dilemma becomes easy to solve.
Very nice post. I enjoyed every part of it. Everything was top notch clean, the personnel was courteous. I highly recommend this post to everybody.
I have seem at least 10 benchmarks showing the same. Do your own research and try to be a little less biased. Latest apache does the same as nginx now. Event driven model with multiple connections handled by a single thread. That is as simple as that and it shouldn't be too hard to understand that using the same techniques, apache will indeed be as fast.
See a more detailed benchmark here: (search for nginx for comparison)
https://people.apache.org/~jim...
easy, google it:
http://www.rootusers.com/web-s...
apache 2.4 in event model can beat nginx in some situation.
Event model is event model whether it is nginx or apache. Most nginx fanboys know nothing about this unfortunately...
Exactly, they have been copying from each other lately anyway so they are close to equivalent in terms of performance. Runtime VMs are runtime VMs.
Well maybe not but they got a less of a Ronald McDonald's like strategy.
http://marketrealist.com/2013/...
> both in ease of administration and more importantly, in performance (why is Apache still spawning processes for every request that comes in..
Apache has had thread model (no need to fork new processes) and EVEN nginx like event model, with fewer/threads than connections for quite a while. Update your info. We run latest IIS and apache on production servers and IIS seems to do pretty well but saying the things you say about apache isn't fair and false in some cases.
In fact, we run instances of apache with event model (max 75 threads, max 4096 connections, keep alive 5 seconds) as a caching reverse proxy and WAF (mod_security) in front of IIS application servers and others. Centralized WAF configuration for all applications and caching so all static content requests rarely hit the application servers.
App server behind the caching reverse-proxy get 2 to 15 work threads, keepalive rarely on, the config is fine tuned with the help of benchmarks and yes, some backend apps are faster with only 2 workers and often degrade with more than 15.
This is a typical performance setup.
Pine rules and filters have been doing this for me since 1995.