Does that check the target of the symlink, or the path to the link itself? I
think the OP was checking the target (or I misunderstood).
--
Stephen Ulmer
Sent from a mobile device; please excuse auto-correct silliness.
> On Mar 8, 2021, at 3:34 PM, Jonathan Buzzard
> wrote:
>
> On
On 08/03/2021 20:45, Jonathan Buzzard wrote:
[SNIP]
So noting that you can write very SQL like statements something like the
following should in theory do it
RULE finddangling LIST dangle WHERE MISC_ATTRIBUTES='L' AND
SUBSTR(PATH_NAME,0,4)='/fs1/'
Note the above is not checked in any way
On 08/03/2021 16:07, Frederick Stock wrote:
CAUTION: This email originated outside the University. Check before
clicking links or attachments.
Presumably the only feature that would help here is if policy could
determine that the end location pointed to by a symbolic link is within
the current
Presumably the only feature that would help here is if policy could determine that the end location pointed to by a symbolic link is within the current file system. I am not aware of any such feature or attribute which policy could check so I think all you can do is run policy to find the
Well - the case here is that the file system has, let’s say, 100M files. Some
percentage of these are sym-links to a location that’s not in this file system.
I want a report of all these off file system links. However, not all of the
sym-links off file system are of interest, just some of them.
Could you use the PATHNAME LIKE statement to limit the location to the files of interest?
Fred___Fred Stock | Spectrum Scale Development Advocacy | 720-430-8821sto...@us.ibm.com
- Original message -From: "Oesterlin, Robert" Sent by:
Looking to craft a policy scan that pulls out symbolic links to a particular
destination. For instance:
file1.py -> /fs1/patha/pathb/file1.py (I want to include these)
file2.py -> /fs2/patha/pathb/file2.py (exclude these)
The easy way would be to pull out all sym-links and just grep for the
