Steps to reproduce
Expected behavior
gci reaches its terminus, and then ceases
Actual behavior
Because of these recursive symlinks,
PS /> ls -la /sys/bus/cpu/devices/cpu0/
lrwxrwxrwx. 1 root root 0 Aug 18 16:12 node0 -> ../../node/node0
PS /> ls -la /sys/bus/cpu/devices/cpu0/node0/
lrwxrwxrwx. 1 root root 0 Aug 18 16:12 cpu0 -> ../../cpu/cpu0
gci eventually runs into something like this:
Directory: /sys/bus/cpu/devices/cpu0/node0/cpu0/node0/cpu0/node0/cpu0/node0/cpu0/node0/cpu0/node0/cpu0/node0/cpu0/nod
e0/cpu0/node0/cpu0/node0/cpu0/node0/cpu0/node0/cpu0/node0/cpu0/node0/cpu0
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 08/18/2016 16:13 cache
It has shown no sign of stopping.
Linux's equivalent ls -lR /sys will cease, as it will not descend into already visited nodes.
Environment data
Name Value
---- -----
PSVersion 6.0 .0 - alpha
PSEdition Core
PSCompatibleVersions {1.0 , 2.0 , 3.0 , 4.0 ...}
BuildVersion 3.0 .0.0
GitCommitId v6.0.0 - alpha.9
CLRVersion
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1 .0.1
Reactions are currently unavailable
Steps to reproduce
Expected behavior
gci reaches its terminus, and then ceases
Actual behavior
Because of these recursive symlinks,
gci eventually runs into something like this:
It has shown no sign of stopping.
Linux's equivalent
ls -lR /syswill cease, as it will not descend into already visited nodes.Environment data