trying to do some testing/sorting of a big ole robocopy script and i need to know where certain symbolic links reside and whether theyre directories or files.
hoping I can somehow filter everything to show me only those files/folders in a given drive/directory? I've used it to great effect to suss out files with system hidden attributes but google hasnt been kind this morning surrounding symbolic links/junctions.
Getting these results can be sped up significantly by enabling Index attributes (Options > Indexes)
is there an equivalent for directories? i have a folder that has symlinks to other folders and attrib:L doesnt cover it. works a treat for symlink'd files though.
huh. wonder why its not picking up any of the symlinked folders ive created. I just tested it on the C drive and youre correct, its picking them up.
however on another drive of mine which has symlink'd folders it does not. any guesses as to why that is? I thought the links might be dead due to migration/moving or some such but tested them and theyre fully functional good symlinks.
You have to do some study on Reparse Points, Symbolic Links, Hardlinks and Junctions aka Softlinks.
Attrib:L are Reparse Points and you can look at the Reparse-Target: and Reparse-Tag: columns to learn more about them.
If the links you're creating are not of this type, they will not be Attrib:L
My memory is rusty but I recommend reading 5 different websites to learn about the differences. Some are for folders only, some are for files only, some are for files or folders.
thanks for the links, ill definitely have to do some reading. they were all/both (files and folders) created via LSE (link shell extension) via "pick link source" then "drop as symbolic link"
here is the folder
Snag_2f6c915.png (42.84 KiB) Viewed 2226 times
here is the folder in everything which shows them as they are
Getting these results can be sped up significantly by enabling Index attributes (Options > Indexes)
Is there any difference between attrib:L and reparse-target: results-wise? Asking because I wold prefer attrib:L precisely because I am indexing attributes.
For the most part, files and folders that have a reparse target will have the L attribute set.
It is technically possible for a NTFS file to have a reparse target without the L attribute set and a file to have no reparse target with the L attribute set.
Placeholder files also obfuscate some attributes and reparse targets.
void wrote: ↑Fri May 26, 2023 12:04 pm
For the most part, files and folders that have a reparse target will have the L attribute set.
It is technically possible for a NTFS file to have a reparse target without the L attribute set and a file to have no reparse target with the L attribute set.
Placeholder files also obfuscate some attributes and reparse targets.
So a comprehensive search that would 100% find all symlinks would be as follows?
void wrote: ↑Fri May 26, 2023 12:04 pm
t is technically possible for a NTFS file to have a reparse target without the L attribute set
If it is not too much off-topic, do you have an example of that? Thought the owner of the reparse tag had to set the attribute too?
(I know there are sybolic links that map to device space (like C:), but those do not appear in Everything).