Hi.
Maybe it's stupid but, have you antivirus?
If yes, check the log messages.
Regards,
-AA
- Original Message -
From: "Mac Bhyat"
To:
Sent: Monday, December 29, 2008 2:46 PM
Subject: [U2] File Delete Logging UV
Hi,
Does anyone know of a way to put file delete logging in place in
Behalf Of Mac Bhyat
> Sent: 30 December 2008 07:48
> To: u2-users@listserver.u2ug.org
> Subject: RE: [U2] File Delete Logging UV
>
> the voc simply vanishes (both DATA and DICT)- as if a
> DELETE.FILE were done
>
> Mac
>
> -Original Message-
> From: own
it's the entire VOC file at unix and uv level
Mac
-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Scott Ballinger
Sent: 29 December 2008 07:21 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] File Delete Loggi
: Re: [U2] File Delete Logging UV
If the deleting process was acting on the &UFD& file, it could quite happily
delete the VOC file, and it would appear as if the file had been deleted via
the operating system as the usual Universe etc links would still exist.
I don't think a VOC tri
You might want to have a look at OS level tools which will monitor a file in
realtime...
something like FAM or Tripwire:
http://oss.sgi.com/projects/fam/faq.html
http://www.blacksheepnetworks.com/security/resources/aix-tripwire.html
If you use AIX, it has an auditing subsystem which would probabl
If the deleting process was acting on the &UFD& file, it could quite happily
delete the VOC file, and it would appear as if the file had been deleted via
the operating system as the usual Universe etc links would still exist.
I don't think a VOC trigger would be enacted if the &UFD& entry was dele
Um, is it the VOC file that is disappearing, or an item in the VOC file?
/Scott Ballinger
Pareto Corporation
Edmonds WA USA
206 713 6006
On Mon, Dec 29, 2008 at 6:24 AM, Jeff Butera wrote:
>
> > Put a DELETE trigger on the VOC file and in the code, specifically test
> for
> > just the VOC item
> Put a DELETE trigger on the VOC file and in the code, specifically test for
> just the VOC item that keeps getting deleted (i.e. ignore any others).
> When you get a hit, immediately send your self an E-mail with all the info
> in question.
>
> Remember that triggers must be globally cataloged,
Put a DELETE trigger on the VOC file and in the code, specifically test for
just the VOC item that keeps getting deleted (i.e. ignore any others). When
you get a hit, immediately send your self an E-mail with all the info in
question.
Remember that triggers must be globally cataloged, but that