search for: 72h

Displaying 7 results from an estimated 7 matches for "72h".

Did you mean: 72
2016 Mar 10
2
Client-initiated secure renegotiation
...ECDHE-RSA-DES-CBC3-SHA:ECDHE-ECDSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_parameters_regenerate = 72h # The !TLSv1 are OK, without TLS not work imtest (cyrus test suit) ssl_protocols = !SSLv2 !SSLv3 # Prefer the server's order of ciphers over client's # Only available on dovecot 2.2.6 and later:: ssl_prefer_server_ciphers = yes # Only available on dovecot 2.2.7 and later:: ssl_dh_parameters...
2016 Jan 21
4
Why is my rsync transfer slow?
...the second file 19:17, almost an hour for a file that is just 32 kB. I don't think the transfer is CPU limited. There are some CPU spikes but generally CPU load is less than 10%. The three rsync processes spawned by this operation has, all in all, used almost exactly 5h of CPU time in the 72h the transfer has been going on. The computer itself idles 23h a day. Nor is memory a problem. Memory pressure has been "green" since the operation begun. Kernel task has accumulated quite a bit of CPU time (57h when I write this), but on the other hand, the uptime is 25 days and all t...
2016 Mar 09
2
Client-initiated secure renegotiation
On 09/03/16 10:44, Florent B wrote: > Hi, > > I don't see any SSL configuration option in Dovecot to disable > "Client-initiated secure renegotiation". > > It is advised to disable it as it can cause DDoS (CVE-2011-1473). > > Is it possible to have this possibility through an SSL option or other ? > > Thank you. > > Florent ssl_protocols = !SSLv3
2016 Jan 21
0
Why is my rsync transfer slow?
...7, almost an hour for a file that is just 32 kB. > > I don't think the transfer is CPU limited. There are some CPU > spikes but generally CPU load is less than 10%. The three rsync > processes spawned by this operation has, all in all, used almost > exactly 5h of CPU time in the 72h the transfer has been going on. > The computer itself idles 23h a day. > > Nor is memory a problem. Memory pressure has been "green" since > the operation begun. > > Kernel task has accumulated quite a bit of CPU time (57h when I > write this), but on the other hand...
2011 Jun 11
1
Amazon AWS, RGenoud, Parallel Computing
Dear R group, since I do only have a moderately fast MacBook and I would like to get my results faster than within 72h per run ( :-((( ), I tried Amazon AWS, which offers pretty fast computers via remote access. I don't want to post any code because its several hundreds lines of code, I am not looking for the "optimal" answer, but maybe some suggestions from you if faced similar problems. I did insta...
2007 Oct 02
3
Logwatch for postfix
On CentOS5 with the latest updates applied, the logwatch filter for postfix returns way too many lines from the log. I get an "unmatched entries" message and all messages that have gone through the system is listed. Here is an example: 8F930A8092: to=<morten at foo.bar>, orig_to=<morten at localhost>, relay=local, delay=0.19, delays=0.06/0.01/0/0.12, dsn=2.0.0,
2013 Jul 31
29
[PATCH 0/9] tools: remove or disable old/useless/unused/unmainted stuff
depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *