-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> The SRV records are currently used for the sub-pools eu.pool and
> na.pool. Before implementing a new approach with a higher degree of
> complexity, that require more effort to implement, I'd appreciate
> feedback on the current implementation. Are t
Hi John,
I attached my changes as a patch. It should not break an existing SKS
installation and it should be easy to compile it for Debian with just a
few easy changes in settings.ml and adding the needed paths to sksconf.
(Changes for the example sksconf for Debian included.)
Then I removed all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I've been playing around with some thoughts on how to improve the
calculation of DNS Service Record (SRV) weights lately[0]. I would,
however, like to make use of the experience of others in continuing
this process.
The SRV records are currentl
John Clizbe wrote:
> Here's the last Debian source deb I looked at, sks_1.1.1+dpkgv3-7. I
> believe the main patch you want is 500_debian_fhs_patch. Debian
> changes locations for most of the SKS files, even names in one or two
> places. A number of these patches have been rolled up into the
> main
Jens Leinenbach wrote:
> Hi,
>
> I compiled SKS 1.1.3. for Debian, but I have a lot of trouble with
> directories.
> SKS seems to set all the files based on the directory configured in the
> basedir variable.
> And a basedir of "." didn't work for me.
>
> So I changed these variables in settings.
Hi,
I compiled SKS 1.1.3. for Debian, but I have a lot of trouble with
directories.
SKS seems to set all the files based on the directory configured in the
basedir variable.
And a basedir of "." didn't work for me.
So I changed these variables in settings.ml:
let basedir = ref "/var/lib/sks"
le
