Question

为什么在执行-f但未执行--silent和--quite时显示错误。有什么区别。我到处搜索但没有发现差异？

root@<containerID>:/crowdLogistics/client/internal# tail --silent ../../logs/gunicorn_internal_client.log 
[2018-09-06 07:06:30 +0000] [69] [INFO] Starting gunicorn 19.6.0
[2018-09-06 07:06:30 +0000] [69] [INFO] Listening at: http://0.0.0.0:8080 (69)
[2018-09-06 07:06:30 +0000] [69] [INFO] Using worker: sync
[2018-09-06 07:06:30 +0000] [74] [INFO] Booting worker with pid: 74
[2018-09-06 07:06:30 +0000] [77] [INFO] Booting worker with pid: 77
[2018-09-06 07:06:30 +0000] [78] [INFO] Booting worker with pid: 78
[2018-09-06 07:06:30 +0000] [81] [INFO] Booting worker with pid: 81
[2018-09-06 07:06:30 +0000] [84] [INFO] Booting worker with pid: 84

root@<containerID>:/crowdLogistics/client/internal# tail --quiet ../../logs/gunicorn_internal_client.log 
[2018-09-06 07:06:30 +0000] [69] [INFO] Starting gunicorn 19.6.0
[2018-09-06 07:06:30 +0000] [69] [INFO] Listening at: http://0.0.0.0:8080 (69)
[2018-09-06 07:06:30 +0000] [69] [INFO] Using worker: sync
[2018-09-06 07:06:30 +0000] [74] [INFO] Booting worker with pid: 74
[2018-09-06 07:06:30 +0000] [77] [INFO] Booting worker with pid: 77
[2018-09-06 07:06:30 +0000] [78] [INFO] Booting worker with pid: 78
[2018-09-06 07:06:30 +0000] [81] [INFO] Booting worker with pid: 81
[2018-09-06 07:06:30 +0000] [84] [INFO] Booting worker with pid: 84

root@<containerID>:/crowdLogistics/client/internal# tail -f ../../logs/gunicorn_internal_client.log 
[2018-09-06 07:06:30 +0000] [69] [INFO] Starting gunicorn 19.6.0
[2018-09-06 07:06:30 +0000] [69] [INFO] Listening at: http://0.0.0.0:8080 (69)
[2018-09-06 07:06:30 +0000] [69] [INFO] Using worker: sync
[2018-09-06 07:06:30 +0000] [74] [INFO] Booting worker with pid: 74
[2018-09-06 07:06:30 +0000] [77] [INFO] Booting worker with pid: 77
[2018-09-06 07:06:30 +0000] [78] [INFO] Booting worker with pid: 78
[2018-09-06 07:06:30 +0000] [81] [INFO] Booting worker with pid: 81
[2018-09-06 07:06:30 +0000] [84] [INFO] Booting worker with pid: 84
tail: unrecognized file system type 0x794c7630 for ‘../../logs/gunicorn_internal_client.log’. please report this to bug-coreutils@gnu.org. reverting to polling

Answer 1

仍然感谢:) @VonC。我找到了解决方案。但这太临时了。

在您的本地docker上遵循以下说明以使tail命令正常工作

cd /root
wget http://ftp.gnu.org/gnu/coreutils/coreutils-8.27.tar.xz && tar xf coreutils-8.27.tar.xz
export FORCE_UNSAFE_CONFIGURE=1
cd /root/coreutils-8.27 && ./configure \
--prefix=/root/coreutils \
--libexecdir=/root/coreutils/lib \
--enable-no-install-program=kill,uptime && make && make install

/root/coreutils/bin/tail -f «filename»

Answer 2

root@<containerID>表示您正在容器会话中（例如，通过docker exec）

从那里，tail -f警告unrecognized file system type可能取决于映像中存在的coreutil版本。有关说明，请参见this answer。

根据执行环境，有patches to coreutils。
就您而言（执行环境是docker），请参见bitnami-docker-tensorflow-serving issue 2

在将Docker与覆盖驱动程序结合使用时发生：Bug 810669：

由使用旧版coreutils的基本映像导致，当将docker与覆盖存储驱动程序一起使用时，导致“ tail: unrecognized file system type 0x794c7630代表“ /var/log/cron.log”。

一旦我们将基础图像从Debian Jessie（旧稳定版）更新为Debian Stretch（稳定版），它可能会得到修复

tail：执行tail -f时，出现无法识别的文件系统类型错误

2 个答案: