Am 02.10.19 um 22:45 schrieb Masaru Kitajima: Oct. 02 16:49:14 v153-127-250-223.vir.kagoya.net systemd[1]: Can't open PID file /var/run/dovecot/master.pid (yet?) after start: Too many levels of symbolic links in old systemd versions that happend when something used in namespaces (ReadOnlyDirectory and friends) was a symlink instead a folder the only expected symlink in that whole path is /var/run pointing to /run [root@srv-rhsoft:/downloads]$ stat /var/run File: /var/run -> ../run Size: 6 Blocks: 0 IO Block: 4096 symbolic link Device: 901h/2305d Inode: 1308336 Links: 1 Access: (0777/lrwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2019-10-01 23:45:01.860264926 +0200 Modify: 2012-06-13 19:12:45.939969537 +0200 Change: 2012-06-13 19:12:45.939969537 +0200 Birth: 2012-06-13 19:12:45.939969537 +0200 [root@srv-rhsoft:/downloads]$ stat /var/run/dovecot File: /var/run/dovecot Size: 480 Blocks: 0 IO Block: 4096 directory Device: 17h/23d Inode: 18004 Links: 5 Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 97/ dovecot) Access: 2019-10-02 22:59:33.767434520 +0200 Modify: 2019-10-02 10:06:18.565093819 +0200 Change: 2019-10-02 10:06:18.565093819 +0200 Birth: - and file a bugreport at Redhat, that should be /run to begin with for a long time anyways, this is not a systemd error, something on your environment or files shipped wioth the distribution is broken _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel