Jason writes:
Since I finally got 2.1.2pl2 working, I decided to upgrade to 3.0.0beta2
(a glutton for punishment, I am). Everything went swimmingly until I
tried to look at any logs or view the config files either for clients or
the general system, via the CGI interface.
Here's what I
Craig Barratt wrote:
Jason writes:
Since I finally got 2.1.2pl2 working, I decided to upgrade to 3.0.0beta2
(a glutton for punishment, I am). Everything went swimmingly until I
tried to look at any logs or view the config files either for clients or
the general system, via the CGI
Jason Hughes writes:
Are you using mod_perl? If so, please restart apache.
Doh! Maybe that would be a good thing to put in the final reminders
after running the configure script? Or detect an upgrade and ask if it
should restart Apache. Everything works great now.
I'll add a message
Since I finally got 2.1.2pl2 working, I decided to upgrade to 3.0.0beta2
(a glutton for punishment, I am). Everything went swimmingly until I
tried to look at any logs or view the config files either for clients or
the general system, via the CGI interface.
Here's what I get from the web
