Hello Sebastian, may I ask for confirmation of the following behaviour:
If Orthanc is manually started for a DB upgrade (say, on Debian:) /usr/sbin/Orthanc --upgrade --trace /etc/orthanc/ BUT the database is already at the required version THEN Orthanc will not run the upgrade and fall back to starting up as if --upgrade was not specified on the command line. The Orthanc book makes me think that when an upgrade is actually run Orthanc will automatically stop after upgrading. If you can confirm that Orthanc does NOT stop if no upgrade is required even if --upgrade is specified then I would like to ask for a change of this behaviour. Typically, one would expect Orthanc to end up in the same state (DB upgraded and server stopped) after an --upgrade run regardless of whether an actual upgrade was performed. https://en.wikipedia.org/wiki/Principle_of_least_astonishment That would make the process predictable and thereby scriptable. The exit code would make it possible to differentiate between success and failure where nothing-to-do-because-up-to-date counts as success. Any chance this can get implemented ? (Should be pretty much a one-liner.) Thanks, Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346