An unnamed Administration source, Brian Witowski, wrote: % Greets, EHLO.
% Since upgrading to Apache 2.0.44, a few things appear to not work any % longer. For instance, trying to start apache from withing Webmin no longer % works. I've looked at the paths in the module configuration and everything % appears to be in order. It gives a message "Failed to start apache", but % upon doing a ps -ax, I have 6 httpd's running. So it appears that it is in % fact running. Which is fine. But since the Webmin module thinks it failed, % I never get the the 'Stop Apached' option, or 'Restart' option for that % matter. I believe this has to do with Webmin trying to scribble in or read from a pid file (normally stored in /var/run). We encountered a similar problem at Caldera, and it turned out to be that Webmin was looking in one location for a pid file and the upgraded Apache was putting the pid file in a different location. After getting Apache and Webmin on the same page in terms of where to look for the pid file, everything was fine. The Apache directive `PidFile' will tell you where Apache puts it, so make sure Webmin is looking in the same place for the same file. % Also, if I attempt to set up virtual hosts (name, not address), it ignores % the virtual hosts and will only allow me to access the default host. I had % two virtual hosts working prior to upgrading. I have given the aliases 'C' % records in bind configuration etc. Can't help you here. % Any pointers or info on using apache 2.x with Webmin 1.070? http://www.webmin.com/ ? :-) Kurt -- If money can't buy happiness, I guess you'll just have to rent it. _______________________________________________ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
