I am looking for a trick to prevent someone (ok, mostly me) from accidentally activating a file that really should not be activated for logging.
I have a handful of files, that would bring the system to it's knees and fill all logs before I could react. For example, one file contains the current status of a bunch of phantoms. Nothing that really needs logging, but there is a tremendously high volume of writes as status flags, counters change. Then there's an ugly file that is nice except for one 650KB(!!) record that is changed all day long. (Yes, I know, change the ap...). Maybe this should be an enhancement request. Charles Stevenson DBA BP/IS Getronics 836 North Street Tewksbury, MA 01876 Tel: 978-858-6872 Fax: 978-858-8631 [EMAIL PROTECTED] www.getronics.com/us The information transmitted is intended only for use by the addressee and may contain confidential and or or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and or or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you. -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
