Le 20-01-2021, à 10:58:54 +0100, to...@tuxteam.de a écrit :
>># find /dev -follow -printf ""
>>find: '/dev/fd/4': No such file or directory
>
>This is funny. At first I thought I could reproduce it by tricking `find'
>into following a broken symlink, but with a "static" setup I couldn't.
>
>Still, /dev/fd is bound to be highly dynamic: it's a link to /proc/self/fd,
>i.e. a view on the current process's open file descriptors. It's quite
>probable that `find' checks some directory entry, and at the time it tries
>to do something with it, it has disappeared, leading to that error
>message.
What is strange is that it is always /dev/fd/4 that is missing, even
after a reboot.
As I said -- this is the own process's set of open file descriptors.
This process in this case is the one running `find' itself. At the
point it is looking for that /proc/fd/4, it is bound to be in some
semi-deterministic state. It's dancing a strange ballet with itself.
Ah ok, I misunderstood that. Very interesting indeed.
I'm sure one could find out exactly what's going on given enough
patience :-)
I' guess so.
My current is to find out why my system is spitting out these 'too many
symnolic links' messages and then fix it.
Thanks a lot for all your explanation !
Steve
