Mercurial > hg > orthanc-book
changeset 875:1006435326a7
new env var for osimis/orthanc
| author | Alain Mazy <am@osimis.io> |
|---|---|
| date | Wed, 21 Sep 2022 11:00:46 +0200 |
| parents | ea6067742d89 |
| children | 9eae6d0b8032 900033cffeb2 |
| files | Sphinx/source/users/docker-osimis.rst |
| diffstat | 1 files changed, 12 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/Sphinx/source/users/docker-osimis.rst Wed Aug 31 18:05:33 2022 +0200 +++ b/Sphinx/source/users/docker-osimis.rst Wed Sep 21 11:00:46 2022 +0200 @@ -115,7 +115,18 @@ - ``MALLOC_ARENA_MAX=10`` will :ref:`control memory usage <scalability-memory>` - ``ORTHANC_JSON`` can be used to pass a JSON "root" configuration (see below). - ``BEFORE_ORTHANC_STARTUP_SCRIPT`` can be used to `run a custom script <https://groups.google.com/g/orthanc-users/c/EXjTq2ZU1vw/m/02CwW1jzAQAJ>`__ before starting Orthanc. - +- ``FORCE_HOST_ID`` and ``GENERATE_HOST_ID_IF_MISSING`` can be used to control the content of /etc/hostid (introduced in 22.9.1). + DCMTK calls gethostid() when generating DICOM UIDs (used, e.g, in modifications/anonymizations). + When /etc/hostid is missing, the system tries to generate it from the IP of the system. + On some system, in particular circumstances, we have observed that the system performs a DNS query + to get the IP of the system. This DNS can timeout (after multiple with retries) and, in particular cases, + we have observed a delay of 40 seconds to generate a single DICOM UID in Orthanc. + Therefore, if /etc/hostid is missing, the startup script creates it and fill it with a random number (default behaviour). + This behaviour can still be deactivated by defining ``GENERATE_HOST_ID_IF_MISSING=false``. + The host id can also be forced by defining ``FORCE_HOST_ID``. + + + Configuration files -------------------