[Bug 303740] New: postgresql akonadi backend does not start if hostname changes

[luisfe]

https://bugs.kde.org/show_bug.cgi?id=303740

            Bug ID: 303740
          Severity: normal
           Version: 1.7.2
          Priority: NOR
          Assignee: kdepim-bugs at kde.org
           Summary: postgresql akonadi backend does not start if hostname
                    changes
    Classification: Unclassified
                OS: Linux
          Reporter: lftabera at yahoo.es
          Hardware: Debian testing
            Status: UNCONFIRMED
         Component: general
           Product: Akonadi

if the hostname of the computer changes then akonadi does not start. The
problem seems that the socket address

/home/[user]/.local/share/akonadi/socket-[hostname]

is harcoded in 
.local/share/akonadi/db_data/postgresql.conf

as

unix_socket_directory = '/home/[user]/.local/share/akonadi/socket-[hostname]'

Reproducible: Always

Steps to Reproduce:
1. Create a new empty user /akonadi configuration with postgresql backend and
default options.
2. Change the hostname of the computer.
3. Reboot
Actual Results:  
postgresql refuses to start with error 

stdout: "esperando que el servidor se inicie....FATAL:  no se pudo crear el
archivo de bloqueo
«/home/user/.local/share/akonadi/socket-oldhostname/.s.PGSQL.5432.lock»: No
existe el fichero o el directorio

Expected Results:  
hostname changes should not affect akonadi. It does not for .kde/
socket-cache-tmp symlinks

-- 
You are receiving this mail because:
You are the assignee for the bug.