Jump to content

hdi-kw

Approved members
  • Posts

    3
  • Joined

  • Last visited

About hdi-kw

hdi-kw's Achievements

Newbie

Newbie (1/5)

0

Reputation

  1. If the old file had a different owner it would make sense. The owner of the file now must be the same user as the user that runs the webserver. If it is a multiuser system you should also change the permission of the file to 440 or even 400 so that not everyone with access to the server can read the configuration file with the DB password inside.
  2. 644 is still write permission for the owner of the file. If the owner is the same as the webserver user then it is not locked. Try 444 to lock this file and only allow read access to it.
  3. I wanted to try to reduce the database size a bit before doing the upgrade to Revive Adserver. Our old openX Source database was over 12GB with nearly all the size of it in the table data_summary_ad_zone_assoc. After reading the function _pruneDataSummaryAdZoneAssocInactiveExpired() I found out I had to change some of our old campaigns that had an end date, but also still had a value in target_*. The next maintenance run dropped the table size to 5,2GB already. There are still a lot of entries in this table with expired even back in 2008. Is there more that should get pruned there? In lib/OA/Maintenance/Pruning.php there is a function _pruneDataSummaryAdZoneAssocOldData() which deletes old entries, but why only zone_id=0? What is zone_id=0 and why not the others? Any ideas what else to do to reduce the size? Thank you very much for your ideas.
×
×
  • Create New...