vndb/yhdev
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ncdc 1.12 released.

Browse source
This commit is contained in:
Yorhel 2012-07-10 15:17:53 +02:00
parent e82b277935
commit 1ac0600f93
10 changed files with 109 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

38
dat/ncdc-faq
View file

@ -34,7 +34,7 @@ For ADC: BASE, RF, TIGR, BZIP, ADCS, KEYP and SUDP.
For NMDC: NoGetINFO, NoHello, UserIP2, MiniSlots, XmlBZList, ADCGet, TTHL and TTHF.
ncdc also support TLS-enabled connections for both hub connections and
ncdc also supports TLS-enabled connections for both hub connections and
client-to-client connections on both ADC and NMDC protocols. Note that ncdc
does not support some of the older NMDC protocol features, like $Get,
$GetZBlock, $CHUNK, $Cancel or non-XML file lists. I am not aware of an other
@ -48,11 +48,11 @@ up-to-date client that still uses any of these features.
=head2 This "Generating certificates..." is taking ages!
When starting up ncdc for the first time, it will need to generate a TLS
certificate. If you're on Linux, GnuTLS will use C</dev/random> to obtain
random bytes. Unfortunately, this can be horribly slow, and in extreme cases it
may take up to an hour before the certificate has been generated. GnuTLS does
not provide a way to use a faster but less secure alternative, so here are some
tips to speed it up or cheat a little.
certificate. If you're on Linux, some versions of GnuTLS may use C</dev/random>
to obtain random bytes. Unfortunately, this can be horribly slow, and in
extreme cases it may take up to an hour before the certificate has been
generated. GnuTLS does not provide a way to use a faster but less secure
alternative, so here are some tips to speed it up or cheat a little.
B<Speed it up:> If you're on a desktop, the general advise is to do something
else on the background so that Linux can generate more data. For example, move
@ -74,8 +74,26 @@ random numbers, this trick should be perfectly fine.
=head2 Ncdc crashes a lot!
Since version 1.10, it shouldn't crash at all. Please report a bug. (If you're
running an older version, please upgrade!)
Since version 1.10, the following crashes are possible:
=over
=item * You're using an old GnuTLS version (< 2.10 or so, you can check this
with C<ncdu --version>), and you have tls_policy enabled. To fix this, upgrade
GnuTLS or C</set tls_policy disabled>. (Bug L<#11|http://dev.yorhel.nl/ncdc/bug/11>).
=item * You're running ncdc on an old system. FreeBSD <= 8.0 and Mac OS X <=
10.5 are known to be problematic. To get around this, upgrade your system or
bug me hard enough to come with a fix within ncdc. (Bug
L<#14|http://dev.yorhel.nl/ncdc/bug/14>).
=item * You were typing a C</search> command but forgot to provide a query.
This crash will be fixed soonish.
=back
If you're running an older version of ncdc, please upgrade! If your ncdc is up
to date and still have a crash not described here, please report a bug.
=head2 Ncdc uses too much disk space!
@ -110,7 +128,9 @@ monthly cron job.
No, ncdc uses its own configuration and hash storage directory. However, on
popular demand I could write a conversion utility to transfer the hash data
from other clients to ncdc's format.
from other clients to ncdc's format. (Contrary to my expectations, there hasn't
been much interest in such a tool ever since I wrote this FAQ entry a year ago.
So I guess this isn't really a FAQ).
=head2 Can ncdc run in the background / as a daemon?