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

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

    <bug>
          <bug_id>2406</bug_id>
          
          <creation_ts>2003-03-22 20:28:15 +0300</creation_ts>
          <short_desc>dhcpcd not compatible with chrooted resolver</short_desc>
          <delta_ts>2004-03-22 13:14:44 +0300</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>4</classification_id>
          <classification>Development</classification>
          <product>Sisyphus</product>
          <component>dhcpcd</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>minor</bug_severity>
          <target_milestone>---</target_milestone>
          
          <blocked>3005</blocked>
          <everconfirmed>1</everconfirmed>
          <reporter name="Michael Shigorin">mike</reporter>
          <assigned_to name="Dmitry V. Levin">ldv</assigned_to>
          <cc>mike</cc>
    
    <cc>rider</cc>
    
    <cc>sem</cc>
          
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>2186</commentid>
    <comment_count>0</comment_count>
    <who name="Michael Shigorin">mike</who>
    <bug_when>2003-03-22 20:28:15 +0300</bug_when>
    <thetext>when network interface is configured via DHCP first time, chrooted environments can get outdated and resolving may not work as a consequence.

\&amp;quot;cheap\&amp;quot; workaround could be running update_chrooted after dhcpcd in networking scripts, but proper one seems to involve dhcpcd.exe script as per documentation.
---

---
this is a practical and not theoretical prob^Wglitch.
</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10304</commentid>
    <comment_count>1</comment_count>
    <who name="Dmitry V. Levin">ldv</who>
    <bug_when>2003-10-20 13:27:36 +0400</bug_when>
    <thetext>*** Bug 3184 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10317</commentid>
    <comment_count>2</comment_count>
    <who name="Michael Shigorin">mike</who>
    <bug_when>2003-10-20 15:06:10 +0400</bug_when>
    <thetext>(see also rider&apos;s comments on #3184)

would be the best if we could figure out whether resolv.conf has changed and run
update_chrooted only when it is so.  some backup &amp; cmp should do.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10323</commentid>
    <comment_count>3</comment_count>
    <who name="Dmitry V. Levin">ldv</who>
    <bug_when>2003-10-20 19:50:26 +0400</bug_when>
    <thetext>Try 1.3.22pl4-alt1 </thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10334</commentid>
    <comment_count>4</comment_count>
    <who name="Michael Shigorin">mike</who>
    <bug_when>2003-10-22 15:08:54 +0400</bug_when>
    <thetext>verified as fixed in dhcpcd-1.3.22pl4-alt1</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>