| 
            Last change
 on this file since 242 was             27, checked in by rainer, 20 years ago           | 
        
        
          | 
             
Support for server-to-server relay and more user policies 
 
           | 
        
        
          | 
            File size:
            1.2 KB
           | 
        
      
      
| Line |   | 
|---|
| 1 | 
 | 
|---|
| 2 | since 2.2.0: server-to-server relay is possible
 | 
|---|
| 3 | 
 | 
|---|
| 4 |   -- this implies that problems will arise if your server is misconfigured
 | 
|---|
| 5 |      to connect to itself (SetExportSeverity is explicitely set
 | 
|---|
| 6 |      to a threshold different from 'none', and the logserver is set to 
 | 
|---|
| 7 |      localhost). The server may deadlock in this case.
 | 
|---|
| 8 | 
 | 
|---|
| 9 | 
 | 
|---|
| 10 | 
 | 
|---|
| 11 | since 2.1.0: update and daemon mode can be combined
 | 
|---|
| 12 | 
 | 
|---|
| 13 |   -- this implies that '-t update' will start a daemon process if running as
 | 
|---|
| 14 |      daemon is the default specified in the config file. use '--foreground'
 | 
|---|
| 15 |      to avoid starting a daemon process
 | 
|---|
| 16 | 
 | 
|---|
| 17 | 
 | 
|---|
| 18 | 
 | 
|---|
| 19 | from 1.7.x to 1.8.x: client/server encryption protocol has been enhanced
 | 
|---|
| 20 | 
 | 
|---|
| 21 |   -- 1.7.x clients can connect to a 1.8.x server
 | 
|---|
| 22 | 
 | 
|---|
| 23 |   -- 1.8.x clients can only connect to a 1.7.x server, if they
 | 
|---|
| 24 |      are built with --enable-encrypt=1
 | 
|---|
| 25 | 
 | 
|---|
| 26 | 
 | 
|---|
| 27 | 
 | 
|---|
| 28 | from 1.6.x to 1.7.x: things to watch out for
 | 
|---|
| 29 | 
 | 
|---|
| 30 |   -- the log server drops root privileges after startup; it needs a logfile
 | 
|---|
| 31 |      directory with write access for the unprivileged user now
 | 
|---|
| 32 | 
 | 
|---|
| 33 |   -- the PID file does not double as lock for the log file anymore; the
 | 
|---|
| 34 |      log file has its own lock now (same path, with .lock appended)
 | 
|---|
| 35 | 
 | 
|---|
| 36 |   -- by default, the HTML status page of the server is in the log directory 
 | 
|---|
| 37 |      now; this allows to make the data directory read-only for the server
 | 
|---|
| 38 | 
 | 
|---|
       
      
  Note:
 See   
TracBrowser
 for help on using the repository browser.