Using master from 4 days ago (currently at fd7adf7) and using the psql backend

Something unusual appeared a couple weeks ago. After running akonadictl stop, the psql server doesn't stop.

I've cleaned my tmp dir, restarted the machine and looked at what happens:

# ls -l /tmp 
total 0
drwxr-xr-x 1 krop krop  62 août   1 09:46 akonadi-krop.FW8sFp
drwx------ 1 krop krop  40 août   1 09:46 akonadi-krop.o6TLY9

and

# ll /tmp/akonadi-krop.FW8sFp 
total 0
# ll /tmp/akonadi-krop.o6TLY9 
total 0
srwxr-xr-x 1 krop krop 0 août   1 09:46 akonadiserver.socket


/home/krop/.local/share/akonadi/socket-$HOSTNAME points to the correct dir

# ps x |grep postgres
 3673 ?        S      0:00 /usr/lib/postgresql93/bin/postgres -D /home/krop/.local/share/akonadi/db_data -k/tmp/akonadi-krop.FW8sFp -h

The command line indicates that this tmp dir should contain the psql socket but it's empty.

Now, after running akonadictl stop, the postgres processes are still there (minus the workers) and

# ls -al /tmp/akonadi-krop.FW8sFp

srwxrwxrwx 1 krop krop   0 août   1 09:46 .s.PGSQL.5432
-rw------- 1 krop krop  86 août   1 09:46 .s.PGSQL.5432.lock

Now the postgres lock & socket files are also there.

# cat /tmp/akonadi-krop.FW8sFp/.s.PGSQL.5432.lock 
3673
/home/krop/.local/share/akonadi/db_data
1406879212
5432
/tmp/akonadi-krop.FW8sFp