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

Jack G. Jolly (jjolly@jjolly.b24b.ingr.com) wrote: : I have found that an SE db can be run with the transaction log file : symbolically linked to /dev/null to avoid it "growing without bound." : Anyone else doing this?? Any "bad things" that coudl happen?? : From your posting it is unclear exactly why you are using a transaction log. The "bad things", which are basicly no rollback work and no rollforward database, are separate solutions to two different problems. If your main concern is to limit the size of the log file, then simply cat(1) /dev/null redirected to the log file periodically. If this is done during a period when no transactions are being processed, no harm will be done. This alternative will allow you to rollback a transaction, which in my opinion is 95% of the value of a transaction log, but not rollforward a database. If you don't need the rollback capability then get rid of transaction logging and the associated overhead. -- ############## __ ######################################################## ####### / / ######## Ron Whiteleather # ###### / / ###### Boise Printer Div. - Formatter Engr. # ##### / /___ ______ ##### # ##### / __ // __ / ##### email: ronw@hpbs2647.boi.hp.com # ##### / / / // /_/ / ##### US Mail: 11411 Chinden Blvd., MS 569 # ##### /_/ /_// ____/ ##### Boise, Idaho 83707 # ##### / / ###### Telnet: 1-323-3476 Fax: (208)323-5277 # ##### / / ####### Opinions freely given and worth the price! # ############ /_/ ##########################################################