<?xml version="1.0" encoding="UTF-8" ?>

<bugzilla version="5.2"
          urlbase="https://bugzilla.altlinux.org/"
          
          maintainer="jenya@basealt.ru"
>

    <bug>
          <bug_id>401</bug_id>
          
          <creation_ts>2002-01-17 11:33:42 +0300</creation_ts>
          <short_desc>dhcpxd doesn\&apos;t run correctly in ifup</short_desc>
          <delta_ts>2003-08-25 15:18:26 +0400</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>4</classification_id>
          <classification>Development</classification>
          <product>Sisyphus</product>
          <component>initscripts</component>
          <version>unstable</version>
          <rep_platform>all</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>CLOSED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P4</priority>
          <bug_severity>major</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Mikhail Zabaluev">mhz</reporter>
          <assigned_to name="Dmitry V. Levin">ldv</assigned_to>
          
          
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>378</commentid>
    <comment_count>0</comment_count>
    <who name="Mikhail Zabaluev">mhz</who>
    <bug_when>2002-01-17 11:33:42 +0300</bug_when>
    <thetext>By default, dhcpxd forks itself in the background, even before the configuration is done. This:
1) doesn\&apos;t play good with initlog -- dhcpxd appears to block on output;
2) doesn\&apos;t fit into the service startup model -- the ifup script should not return until the interface is either configured, or failed to configure.Fortunately, there is -w option that prevents dhcpxd from forking. The timeout in case of dead Ethernet is not prolonged, so I think it should be OK to wait for a while.
A patch is provided for clarity.
---

---

</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>3031</commentid>
    <comment_count>1</comment_count>
    <who name="Dmitry V. Levin">ldv</who>
    <bug_when>2002-01-18 12:47:19 +0300</bug_when>
    <thetext>Thanks,
fixed in initscripts-5.49-ipl38mdk.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>6396</commentid>
    <comment_count>2</comment_count>
    <who name="Dmitry V. Levin">ldv</who>
    <bug_when>2002-01-18 12:47:19 +0300</bug_when>
    <thetext>Thanks,
fixed in initscripts-5.49-ipl38mdk.</thetext>
  </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>32</attachid>
            <date>2002-01-17 11:33:42 +0300</date>
            <delta_ts>2002-01-17 11:33:42 +0300</delta_ts>
            <desc>0000401-ifup-dhcpxd.patch</desc>
            <filename>0000401-ifup-dhcpxd.patch</filename>
            <type>application/octet-stream</type>
            <size>0</size>
            <attacher name="Mikhail Zabaluev">mhz</attacher>
            
              <data encoding="base64"></data>

          </attachment>
      

    </bug>

</bugzilla>