Peter Bieringer

https://github.com/Kozea/Radicale/pull/1328 merged today

I assume yes, this is also required for a lot of other daemons which at least requires "reload" or "restart" (depending on internal implementation) to release their current server socket...

@Semmelrocks : have you checked any other log event which is stored by `syslog-ng` into another file...potentially `syslog-ng` started before timesync was successful and did not update it's internal time...

I have such in use since years, based on using softlinks Directory: /var/lib/radicale/collections/collection-root ``` user1 user2 groups ``` Directory: /var/lib/radicale/collections/collection-root/groups ``` group-1.ics group-1.vcf group-2.ics group-2.vcf ``` Directory: /var/lib/radicale/collections/collection-root/user1 ``` user1.ics...

according to examples it should work: ``` [server] # CalDAV server hostnames separated by a comma # IPv4 syntax: address:port # IPv6 syntax: [address]:port # For example: 0.0.0.0:9999, [::]:9999 ```...

> It is about using IPv4 address directly. This `localhost:9999` works. This `127.0.0.1:9999` doesn't work. that is working definitly on Linux with python 3.8 ona dualstack system. Question would by...

This can be related to https://github.com/Kozea/Radicale/issues/1313, which was solved finally by reworking the server socket listen code, can you please test 3.1 "latest"?

issue solved or still persisting? I have not seen such files on my server.

are you using 3.1.latest and are the tmp files occuring again?

@mpasternak : this PR has conflicts, please rebase, thank you!