-
Don't re-download notification.xml in case ETag says that it's not needed.
-
[HTTP 304](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/304) is treated as an error because Fort assumes a successful download implies there's a [file to rename](https://github.com/NICMx/F…
-
It was found that the Krill 0.9.0 publication server locks on requests.
This issue seems to be related to unexpectedly slow deserialisation of the repository content state. This issue primarily aff…
-
Currently krill-sync supports *getting* any notification file from a given URI, but it uses `notification.xml` when writing the file. It should use the filename given in the URI instead.
Note: this…
-
> xml-rs is Unmaintained
| Details | |
| ------------------- | ---------------------------------------------- |
| Status | unm…
-
Krill in testing deployment with more than 50 parents in one CA.
CPU utilization stays at 100% for only one core. (Powerful server with 8 x 3GHz cores)
Krill is constantly cycling through:
- …
-
An idea..
If operators simply use something like NGINX as a caching server then load balancing becomes easier. In particular: no more sticky sessions would be needed: get notification.xml from node…
-
fort 1.5.3 (installed from fort-1.5.3-1.el8.x86_64.rpm)
Started to crash repeatedly beginning about a hour ago.
Unable to get it working.
Tried to wipe /var/fort_cache, did not help
> Stack…
-
**Describe the bug**
When running ``make check VERBOSE=1`` (on amd64), I'm seeing several compiler warnings of the following categories:
- incompatible-pointer-types
- format-truncation=
- strin…
-
I install
```
[nlnetlabs]
name=NLnet Labs
baseurl=https://packages.nlnetlabs.nl/linux/centos/8/main/x86_64
enabled=1
sudo rpm --import https://packages.nlnetlabs.nl/aptkey.asc
sudo yum ins…