File: OldLockingMechanism.txt

package info (click to toggle)
orthanc-postgresql 2.0-3
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 884 kB
  • ctags: 2,083
  • sloc: cpp: 5,313; ansic: 3,582; python: 381; sql: 150; sh: 38; makefile: 27
file content (38 lines) | stat: -rw-r--r-- 1,140 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
LOCKING
=======

This text file archives information about the locking mechanism in the
initial release of the PostgreSQL plugins. THIS INFORMATION IS NOT
VALID ANYMORE!


>>>>>>>>

The plugins implement a locking system to prevent other instances of Orthanc from using the same PostgreSQL database. If for some reason, Orthanc has not properly shutdown (for instance because of a power outage), you will have to manually unlock the database. This can be done by adding the `--unlock` flag at the command line:

{{{
# ./Orthanc Configuration.json --unlock
}}}

If you dislike the locking mechanism and wish to disable it, set the "`Lock`" option to `false` in the configuration:

<code language="json">
{
  "Name" : "MyOrthanc",
  [...]
  "PostgreSQL" : {
    "Lock" : false,
    "EnableIndex" : true,
    "EnableStorage" : true,
    "Host" : "localhost",
    "Port" : 5432,
    "Database" : "orthanc",
    "Username" : "orthanc",
    "Password" : "orthanc"    
  },
  "Plugins" : [
    "/home/user/OrthancPostgreSQL/Build/libOrthancPostgreSQLIndex.so",
    "/home/user/OrthancPostgreSQL/Build/libOrthancPostgreSQLStorage.so"
  ]
}
</code>