https://issues.apache.org/bugzilla/show_bug.cgi?id=45863
--- Comment #12 from MOB.COM <[EMAIL PROTECTED]> 2008-09-23 18:43:45 PST --- (In reply to comment #11) > > So this can be a very common problem across ALL major Linux distros, that is > > confusing and time consuming to debug and fix for new users. > > When I configure an invalid PidFile in 2.2.8, a message is logged to the > errorlog and Apache exits. mod_cgi's cgid daemon was left stranded, but it > did > not keep listening ports open. I > in 2.2.9 it keeps listening ports open. > What makes you think it's common for people to have invalid PidFiles > configured, whether they come from a vendor or are compiled and configured by > users? Most people import their vendor httpd.conf over to the source installation rather than re-typing everything manually. > I posit that it's a very slim minority of "listening port..." errors > that are a result of some mismanagement of the pidfile. > I can not argue how popular this problem is, but I do think it is a complicated problem to solve for users who are new to building Apache from source and can give a negative first impression about Apache. Imho. the user-friendliest solution would be to have Apache try the ASF layout Pidfile path if the vendor path set in httpd.conf does not work and notify the user of the problem. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
