Buffered Error Log
Posted in 1991
We have a background process written in 4gl that occasionally hits a lock on one of the tables. This lock is normally released after a minute or so as it is held by a user updating rows through a screen. We loop on the lock every 30 seconds until released. We also write a message to the Informix Error log using the errorlog() function every 5 minutes to warn the supervisor that somebody has walked away from their terminal while the row is still locked. We intend to tail the error log to a printer near the supervisor so that any errors that occur are noticed quickly. The problem with this method is that the log appears to be buffered in some way so that the lock messages do not appear in the error file (and on the printer) until after the lock is released. We don't want to go to the trouble of writing a completely different error log and merging them to the same printer so if anyone knows how to stop this buffering of the error log it would be very useful to us. Thanks in advance, Jim -------------------------------------------------------------------- Name: Jim Gordon Internet: jgordon@ssf-sys.DHL.COM Company: DHL Systems Inc Phone: (415) 358-5911 Address: 1700 S. Amphlett Blvd. Fax: (415) 571-6429 San Mateo, CA 94402 --------------------------------------------------------------------