<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: netconf in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/netconf/m-p/2438364#M6209</link>
    <description>Steve,&lt;BR /&gt;&lt;BR /&gt;Rerunning the startup script '/sbin/init.d/net start'&lt;BR /&gt;&lt;BR /&gt;pretty much reconfigures everything from a modified netconf but it may depend on exactly what you've changed.&lt;BR /&gt;&lt;BR /&gt;ifconfig lan? down disables the interface and up re-enables it, nothing to do with netconf.&lt;BR /&gt;&lt;BR /&gt;If you look at the 'net' script in /sbin/init.d you will see that amongst other things it calls 'ifconfig' to configure the relevant interfaces.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;John</description>
    <pubDate>Mon, 21 Aug 2000 20:55:38 GMT</pubDate>
    <dc:creator>John Palmer</dc:creator>
    <dc:date>2000-08-21T20:55:38Z</dc:date>
    <item>
      <title>netconf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/netconf/m-p/2438363#M6208</link>
      <description>Howdy Everyone,&lt;BR /&gt;&lt;BR /&gt;Hopefully a quick question.  Can I avoid a restart after making changes to my netconf file?  Does ifconfig lan1 down/up cause it to re-read the file or do I need to stop/start a daemon?  Right now I'm restarting to be sure, but I'd love to avoid the stop/start wait :)&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Steve</description>
      <pubDate>Mon, 21 Aug 2000 20:46:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/netconf/m-p/2438363#M6208</guid>
      <dc:creator>Steve Sauve</dc:creator>
      <dc:date>2000-08-21T20:46:58Z</dc:date>
    </item>
    <item>
      <title>Re: netconf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/netconf/m-p/2438364#M6209</link>
      <description>Steve,&lt;BR /&gt;&lt;BR /&gt;Rerunning the startup script '/sbin/init.d/net start'&lt;BR /&gt;&lt;BR /&gt;pretty much reconfigures everything from a modified netconf but it may depend on exactly what you've changed.&lt;BR /&gt;&lt;BR /&gt;ifconfig lan? down disables the interface and up re-enables it, nothing to do with netconf.&lt;BR /&gt;&lt;BR /&gt;If you look at the 'net' script in /sbin/init.d you will see that amongst other things it calls 'ifconfig' to configure the relevant interfaces.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;John</description>
      <pubDate>Mon, 21 Aug 2000 20:55:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/netconf/m-p/2438364#M6209</guid>
      <dc:creator>John Palmer</dc:creator>
      <dc:date>2000-08-21T20:55:38Z</dc:date>
    </item>
    <item>
      <title>Re: netconf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/netconf/m-p/2438365#M6210</link>
      <description>With ifconfig down/up you can avoid the reboot and get the desired modification.&lt;BR /&gt;/sbin/init.d/net stop/start is going to check what you've done. Not reboot is necessary. You might need to stop/restart /sbin/init.d/nfs.core or other scripts, depends on what you modified. But, basically, /sbin/init.d/net is enough.</description>
      <pubDate>Mon, 21 Aug 2000 21:13:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/netconf/m-p/2438365#M6210</guid>
      <dc:creator>Antoanetta Naghiu</dc:creator>
      <dc:date>2000-08-21T21:13:41Z</dc:date>
    </item>
    <item>
      <title>Re: netconf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/netconf/m-p/2438366#M6211</link>
      <description>The ifconfig command and the /sbin/init.d/net stop/start will avoid a reboot.</description>
      <pubDate>Tue, 22 Aug 2000 01:53:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/netconf/m-p/2438366#M6211</guid>
      <dc:creator>Rick Garland</dc:creator>
      <dc:date>2000-08-22T01:53:54Z</dc:date>
    </item>
    <item>
      <title>Re: netconf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/netconf/m-p/2438367#M6212</link>
      <description>Be carefull not to do the "/sbin/init.d/net stop" from a remote connection (like telnet) because you may lost the connection before issuing the "/sbin/init.d/net start" command.&lt;BR /&gt;&lt;BR /&gt;Alternatively you could try something like "/sbin/init.d/net stop &amp;amp;&amp;amp; /sbin/init.d/net start".</description>
      <pubDate>Tue, 22 Aug 2000 02:52:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/netconf/m-p/2438367#M6212</guid>
      <dc:creator>Philip Chan_1</dc:creator>
      <dc:date>2000-08-22T02:52:03Z</dc:date>
    </item>
    <item>
      <title>Re: netconf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/netconf/m-p/2438368#M6213</link>
      <description>As mentionned above, since you cant stop throught remote connexion if you dont have access to the console, use at/cron to execute your stop/start cmd&lt;BR /&gt;Godd luck</description>
      <pubDate>Tue, 22 Aug 2000 10:06:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/netconf/m-p/2438368#M6213</guid>
      <dc:creator>Victor BERRIDGE</dc:creator>
      <dc:date>2000-08-22T10:06:11Z</dc:date>
    </item>
  </channel>
</rss>

