Added article section + SQLite threading article + minor ncdc FAQ fixes
This commit is contained in:
parent
291c0ea142
commit
f1f08a5fe0
3 changed files with 693 additions and 4 deletions
|
|
@ -16,7 +16,7 @@ mentioned projects are dead: neither LDCC, DCTC nor TurboVision are seeing any
|
|||
recent development.
|
||||
|
||||
L<ShakesPeer|http://shakespeer.bzero.se/> - Appears to have a commandline
|
||||
inter-face as well. I haven't personally tried it, but have not heard much
|
||||
interface as well. I haven't personally tried it, but have not heard many
|
||||
positive things about it. Has not seen any recent development, either.
|
||||
|
||||
|
||||
|
|
@ -61,8 +61,8 @@ And then follow the instructions in the README.
|
|||
Most likely this is caused by a L<bug in
|
||||
glib-networking|https://bugzilla.gnome.org/show_bug.cgi?id=664321>. To get
|
||||
around it, install the "certtool" utility that comes with gnutls (package
|
||||
"gnutls-bin" on Ubuntu), delete the old certificates ("rm ~/.ncdc/cert/*"), and
|
||||
then start ncdc again.
|
||||
"gnutls-bin" on Ubuntu), delete the old certificates (C<rm ~/.ncdc/cert/*>),
|
||||
and then start ncdc again.
|
||||
|
||||
|
||||
=head2 Why doesn't ncdc rotate log files automatically?
|
||||
|
|
@ -109,7 +109,7 @@ the DC Development hub before ncdc had native TLS support:
|
|||
accept = 127.0.0.1:16591
|
||||
connect = hub.dcbase.org:16591
|
||||
|
||||
The URL `adc://127.0.0.1:16591/' can then be used to connect to the hub from
|
||||
The URL C<adc://127.0.0.1:16591/> can then be used to connect to the hub from
|
||||
within ncdc.
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue