After rechecking all paths, I would:

rm /etc/rc.d/rc3.d/S11apache2
ln -s /etc/rc.d/apache2 /etc/rc.d/rc3.d/S99apache2

Be aware of all occurrences of K11apache2 (or equivalent) also.
Now apache2 will be (close to) the last service started in run level 3.


  ----- Original Message ----- 
  From: john 
  To: users@httpd.apache.org 
  Sent: Wednesday, January 10, 2007 11:45 AM
  Subject: RE: [EMAIL PROTECTED] Name Resolution error


  The script is /etc/rc.d/rc3.d/S11apache2 -> ../apache2



  I feel that the priority of the apache's beginning was unexpectedly changed 




------------------------------------------------------------------------------

  From: Jonathan Mangin [mailto:[EMAIL PROTECTED] 
  Sent: Wednesday, January 10, 2007 5:27 PM
  To: users@httpd.apache.org
  Subject: Re: [EMAIL PROTECTED] Name Resolution error



  I didn't receive a copy of your last post, but I'm going to pretend

  you're talking to me.  (Please, BTW, use plain text for posts.)

  In /etc/rc3.d (or wherever) what is the name of your apache

  startup script?



    ----- Original Message ----- 

    From: john 

    To: users@httpd.apache.org 

    Sent: Wednesday, January 10, 2007 8:55 AM

    Subject: RE: [EMAIL PROTECTED] Name Resolution error



    I totally agree with you.



    My system is an opensuse 10.1 and I didn't have any problem until the last 
update through YOU.



    Do you experience any similar problem?




----------------------------------------------------------------------------

    From: Jonathan Mangin [mailto:[EMAIL PROTECTED] 
    Sent: Tuesday, January 09, 2007 4:56 PM
    To: users@httpd.apache.org
    Subject: Re: [EMAIL PROTECTED] Name Resolution error



    Sorry about that.

      ----- Original Message ----- 

      From: john 

      To: users@httpd.apache.org 

      Sent: Tuesday, January 09, 2007 2:37 AM

      Subject: RE: [EMAIL PROTECTED] Name Resolution error



      HostnameLookups is for logging.



      I have other systems with many virtual hosts and there is no problem at 
all.



      Is there any possibility that when apache starts (runlevel 3) cannot 
resolve the host names.



      If I shut the apache (having resolution problem) and then just restart 
it, everything works fine.






--------------------------------------------------------------------------

      From: joseph c [mailto:[EMAIL PROTECTED] 
      Sent: Tuesday, January 09, 2007 7:48 AM
      To: users@httpd.apache.org
      Subject: Re: [EMAIL PROTECTED] Name Resolution error



      how about the value of the "HostnameLookups", it should set to "Off"

      On 1/9/07, john <[EMAIL PROTECTED] > wrote:

      Hi all

      I have installed apache 2.2.3

      Apache starts automatically, so there is an error 

      [Mon Jan 08 20:11:27 2007] [error] (EAI 3)Temporary failure in name
      resolution: Could not resolve host name DomainName1 -- ignoring!
      [Mon Jan 08 20:11:27 2007] [error] (EAI 3)Temporary failure in name
      resolution: Could not resolve host name DomainName2-- ignoring! 


      DomainName1 and DomainName2 are the names for my virtual hosts.

      After that error I have to reload apache and then everything works fine.



      ------------------------------------

      In /etc/rc3.d I have S99apache2.  Doesn't the 99 have to do

      with the order services are started?  I see in Solaris that

      network services are started in run level 2.


Reply via email to