Mac You can't delete your own VOC file using DELETE.FILE so if it is being done from UniVerse that means it is happening from another account. So you could a) look through other accounts and see if there is a suspicious Q or F pointer to that VOC which might help track down the culprit, or b) wrap the DELETE.FILE command in each of the other accounts so that they are accessed as a Remote item using the security subroutine entry to log the activity.
Brian > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Mac Bhyat > Sent: 30 December 2008 07:48 > To: [email protected] > 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: [email protected] > [mailto:[email protected]] On Behalf Of > dennis bartlett > Sent: 29 December 2008 09:14 PM > To: [email protected] > Subject: 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 trigger would be enacted if the &UFD& > entry was deleted. > > Does the file simply vanish, ie there is nothing present at > O/S level, or is the VOC file simply replaced with a previous > version? A write to the &UFD& file would achieve a > replacement, I don't know if the trigger on the VOC file > would fire.. and a simple copy statement to &UFD& would > achieve that write.. > > A possible way would be to poll the &UFD& file with a process > during the day / time period and observe when it occurs. One > process where this would be regularly done is in a program > running a "menu system" . Alternatively, if the VOC entry is > important, one could write it back into the VOC regularly > during the day... just as an interim measure whilst you > search the galaxy for what will turn out to be a simple answer ;-) > > > > 2008/12/29 Scott Ballinger <[email protected]> > > > 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 <[email protected]> > > wrote: > > > > > <quote who='Israel, John R.' date='Monday 29 December 2008'> > > > > 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 they > > > > can > > call > > > > locally cataloged programs (thus you can have > differences between > > > accounts > > > > by having the subsequent subroutines different between > accounts). > > > > > > > > I hope this helps. > > > > > > I was thinking the same thing, but this doesn't address > the issue if > > > there's an O/S process that's deleting the VOC outside of uv. If > > > the process deleting your VOC is outside of uv, it may be > harder to > > > identify. > > > > > > > > > > > > -- > > > Jeff Butera, Ph.D. > > > Administrative Systems > > > Hampshire College > > > [email protected] > > > 413-559-5556 > > > > > > "Where I'm from, we believe all sorts of > > > things that aren't true. We call it 'history'." > > > The Wizard, Wicked > > > ------- > > > u2-users mailing list > > > [email protected] > > > To unsubscribe please visit http://listserver.u2ug.org/ > > ------- > > u2-users mailing list > > [email protected] > > To unsubscribe please visit http://listserver.u2ug.org/ > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ > > > -- > This message was scanned for spam and viruses by BitDefender. > For more information please visit http://linux.bitdefender.com/ > > > > __________ NOD32 3721 (20081229) Information __________ > > This message was checked by NOD32 antivirus system. > http://www.eset.com > > > > > -- > This message was scanned for spam and viruses by BitDefender. > For more information please visit http://linux.bitdefender.com/ > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
