Re: Unit dovecot.service has failed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Thu, Oct 3, 2019, 06:24 Masaru Kitajima <thirstytraveler@xxxxxxx> wrote:
Mr. Harald

Thank you so much for the detailed information. I tried two commands which
you kindly suggested. The results are as below.

    [root@vhost /var/log]# stat /var/run
    File: `/var/run' -> `../run'
    Size: 6             Blocks: 0          IO Block: 4096   symbolic link
    Device: 9094h/37012d        Inode: 74932926    Links: 1
    Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
    Access: 2019-10-02 19:50:39.000000000 +0900
    Modify: 2019-02-20 18:21:23.000000000 +0900
    Change: 2019-02-20 18:21:23.000000000 +0900
    Birth: -

    [root@vhost /var/log]# stat /var/run/dovecot
    File: `/var/run/dovecot'
    Size: 740           Blocks: 0          IO Block: 4096   directory
    Device: 9169h/37225d        Inode: 4136984558  Links: 5
    Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (   97/ dovecot)
    Access: 2019-10-02 17:20:18.243640196 +0900
    Modify: 2019-10-02 16:50:44.268614218 +0900
    Change: 2019-10-02 16:50:44.268614218 +0900
    Birth: -

I wonder why“British”are not set.

Until very recently, there was no Linux API through which the file's birth time could be retrieved, and `stat` had to always show an empty field.
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux