Re: WebCatalog copies database with -tmp suffix
This WebDNA talk-list message is from 2005
It keeps the original formatting.
numero = 61144
interpreted = N
texte = Justin,This has come up when the "feature" was first introduced. ISTR this exact same question/issue being asked and Scott or someone provided more detailed information, but the setting that is causing all those .tmp db's is in the admin section and is called:"Safe Write for database"Changing that to NO should stop that, but that may or may not be a good thing (depending on if you want the feature to work eh?).I'll let someone else comment further - but it should be in the archives somewhere.GJKAt 09:31 AM 2/23/2005, you wrote:>We're running WebStar 4.4 on Mac OS9 and using WebCatalog 4.51.>>We've had some of the most major problems we've ever had with our server in>the past day. We've found what we think is the culprit, an over abundance>of -tmp suffix database files that have seemed to come out of nowhere.>We've read in the talk-list archives that WebCatalog is attempting to save>database files by copying the file and appending a -tmp suffix on to the end>of it. Furthermore, it then appends an incrementing number on the end of>that save every other time it tries to save resulting in something like>this:>>mydatabase.db-tmp>mydatabase.db-tmp1>mydatabase.db-tmp2>mydatabase.db-tmp3>mydatabase.db-tmp4>>Apparently it's creating another one of these databases everytime someone>accesses a certain part of our code and with traffic being high you can see>how this would cause a major problem and slow down for us.>>We have several hundred databases across the server and it's not doing this>to all of them, it seems to pick and choose which ones WebCatalog wants to>save. We're looking for a reason for this as it has never happened before.>We think it may be as simple as a corrupt database.>>It looks like discussion for this on the talk-list has ended around the year>2000 but we didn't read any thorough conclusion. Has anyone come across>this since then that can shed some light on our problem? We've resulted to>deleting all of the files (over 11,000 of them) in an effort to speed our>servers back up. Thanks.>>Justin Carroll-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list
.To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Justin,This has come up when the "feature" was first introduced. ISTR this exact same question/issue being asked and Scott or someone provided more detailed information, but the setting that is causing all those .tmp db's is in the admin section and is called:"Safe Write for database"Changing that to NO should stop that, but that may or may not be a good thing (depending on if you want the feature to work eh?).I'll let someone else comment further - but it should be in the archives somewhere.GJKAt 09:31 AM 2/23/2005, you wrote:>We're running WebStar 4.4 on Mac OS9 and using WebCatalog 4.51.>>We've had some of the most major problems we've ever had with our server in>the past day. We've found what we think is the culprit, an over abundance>of -tmp suffix database files that have seemed to come out of nowhere.>We've read in the talk-list archives that WebCatalog is attempting to save>database files by copying the file and appending a -tmp suffix on to the end>of it. Furthermore, it then appends an incrementing number on the end of>that save every other time it tries to save resulting in something like>this:>>mydatabase.db-tmp>mydatabase.db-tmp1>mydatabase.db-tmp2>mydatabase.db-tmp3>mydatabase.db-tmp4>>Apparently it's creating another one of these databases everytime someone>accesses a certain part of our code and with traffic being high you can see>how this would cause a major problem and slow down for us.>>We have several hundred databases across the server and it's not doing this>to all of them, it seems to pick and choose which ones WebCatalog wants to>save. We're looking for a reason for this as it has never happened before.>We think it may be as simple as a corrupt database.>>It looks like discussion for this on the talk-list has ended around the year>2000 but we didn't read any thorough conclusion. Has anyone come across>this since then that can shed some light on our problem? We've resulted to>deleting all of the files (over 11,000 of them) in an effort to speed our>servers back up. Thanks.>>Justin Carroll-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Gary Krockover
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
HomePage Caution (1997)
This list needs a digest: rant, rave... (1997)
Writing [raw] to a file (2000)
WebCatalog [FoundItems] Problem - LONG - (1997)
Security Hole (1998)
[Webcat 2]Next (1997)
Multiple prices (1997)
WebCat2.0 acgi vs plugin (1997)
Updating Prices in Online Database (1999)
CommandSecurity? (1997)
test (2002)
Problems appending to database (1997)
WebCat & WebTen (1997)
off topic - dna snipets (1997)
carriage returns in data (1997)
[convertchars] (2000)
Conditional searching & displaying (1997)
[table] retained in memory (2006)
Not really WebCat - need HTML Grider (1997)
Unix Webcat Permission - Suggestions (2000)