Hi, > I still have a problem. I made sure user apache could > read/write in /var/cache/midgard and could read in /var/lib/midgard > the error log (see below) reports midgard is trying to open a > file named: > /var/cache/midgard/5-49-10-0.php > > but it is not on my system. Should it be there? If I knew > more about how midgard was supposed to work, I could provide > more information - sorry
Normally Midgard used to create all HTML-Output on the fly. The Information to display comes from the Mysql-DB. But because creating every page over and over again causes quite a bit of performance caching was introduced. So now generated output gets stored as php-file in the cache directory. Whenever a request is sent to midgard the cached file is served if it exists. (This is just a rough draft...) > [Thu Aug 18 13:40:44 2005] [debug] midgard-apache2.c(1314): > [client 192.168.1.1] Midgard: regenerating > /var/cache/midgard/5-49-10-0.php: cannot open, assuming > non-existant [Thu Aug 18 13:40:44 2005] [debug] > midgard-apache2.c(2259): [client 192.168.1.1] Midgard: > Couldn't create cache file Looks like Apache still is NOT allowed to write to /var/cache/midgard... Are you sure permissions are set correctly? (f.x on SuSE the apache-user is named "wwwrun", apache-group is "www". Not sure what they are named in RHEL...) Have fun, Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
