Re: How to trace Log for IFS / folder -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: How to trace Log for IFS / folder
From: Rob Berendt <robertowenberendt@xxxxxxxxx>
Date: Tue, 27 May 2025 10:23:51 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Which was exactly what he was trying to do.
I think the problem was that he was hoping it didn't require a decoder ring
to get to and was in the simple path name column. The path name only shows
the parent directory with the auditing turned on.

Seems a job for object auditing?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: How to trace Log for IFS / folder , cesco

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.