Re: Running SE with log files linked to /dev/null

In article <1992Oct29.153901.22495@informix.com> davek@informix.com (David Kosenko) writes: >Jack G. Jolly writes: >[ some details deleted] >> >>If we first link the log file to /dev/null, then load the graphics files, >>we don;t have to worry about the log file getting so big that it uses all >>the disk. > >At this point, I have to ask why you are using a log in the first place? >It provides no functionality, and in fact is only serving to >slow down processing (due to writing log records out). You have no >capability to rollback your work. Why not just turn logging off? Keep in mind, Dave, that there IS NO DOCUMENTED WAY to turn off logging in SE; perhaps this is the source of Jack's problem. FYI: to turn off logging in an SE database, do the following as user "informix": 1) set environment 2) isql - - database <dbname> exclusive; begin work; delete from systables where tabid = 0; should respond: "1 row(s) deleted." commit work; (you can rollback instead if you changed your mind) close database; The database logging is now turned "off". >Dave -- Alan Denney aland@informix.com {pyramid|uunet}!infmx!aland Smith and Wesson: the Ultimate Point-and-Click User Interface.