<?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: Changing NIS domain name in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/changing-nis-domain-name/m-p/2430833#M2980</link>
    <description>That is a good point.  Try repushing all mapes (just issue ypmake from the master).  I don't know why that would be necessary, but see what happens.&lt;BR /&gt;&lt;BR /&gt;One last thing -- check /etc/passwd on the server to make sure the last line correctly refers login checks to NIS.</description>
    <pubDate>Fri, 14 Jul 2000 17:13:00 GMT</pubDate>
    <dc:creator>Alan Riggs</dc:creator>
    <dc:date>2000-07-14T17:13:00Z</dc:date>
    <item>
      <title>Changing NIS domain name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/changing-nis-domain-name/m-p/2430829#M2976</link>
      <description>We have just changed our NIS domain name on the fly - which itself wasn't particularly troublesome, except one small problem on machines running HP-UX 11.  The problem is no new users can log in on these machines, ypcat passwd shows the correct entries in the passwd map, but when you do a "su - username" it says "unknown user".  I do realise the quickest solution would be to do a reboot but I can't at the moment due to heavy workload.  Machines running HP-UX 10x didn't require reboots.&lt;BR /&gt;&lt;BR /&gt;Any suggestions?  Thanks.</description>
      <pubDate>Fri, 14 Jul 2000 14:04:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/changing-nis-domain-name/m-p/2430829#M2976</guid>
      <dc:creator>Huiqi Liu</dc:creator>
      <dc:date>2000-07-14T14:04:37Z</dc:date>
    </item>
    <item>
      <title>Re: Changing NIS domain name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/changing-nis-domain-name/m-p/2430830#M2977</link>
      <description>What does domainname return for the server in question?  Does it match your new change?  I asssume you have edited the config files and recycled nis servers and client services on all boxes.  Does ypwhich -m show that maps are being resolved to the proper place?</description>
      <pubDate>Fri, 14 Jul 2000 14:38:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/changing-nis-domain-name/m-p/2430830#M2977</guid>
      <dc:creator>Alan Riggs</dc:creator>
      <dc:date>2000-07-14T14:38:55Z</dc:date>
    </item>
    <item>
      <title>Re: Changing NIS domain name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/changing-nis-domain-name/m-p/2430831#M2978</link>
      <description>Thanks for the reply.&lt;BR /&gt;&lt;BR /&gt;domainname on the machines shows the new, correct domain name.  Yes I restarted all the yp services and ypwhich -m lists the correct maps.  (The config files have been modified too, which I guess will only be read at the next reboot).  "ypmatch newuser passwd" even returns the correct info.  But su - newuser doesn't work (nor telneting and trying to log in as the new user).  Like I said, a reboot will definitely fix it - but what is causing this problem?  Very intriguing.</description>
      <pubDate>Fri, 14 Jul 2000 14:55:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/changing-nis-domain-name/m-p/2430831#M2978</guid>
      <dc:creator>Huiqi Liu</dc:creator>
      <dc:date>2000-07-14T14:55:18Z</dc:date>
    </item>
    <item>
      <title>Re: Changing NIS domain name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/changing-nis-domain-name/m-p/2430832#M2979</link>
      <description>Try to stop and restart nis client.&lt;BR /&gt;/sbin/init.d/nis.client stop and again start.&lt;BR /&gt;Eventually manually push the maps to slaves (if you use nis slave in your config).&lt;BR /&gt;Any better?</description>
      <pubDate>Fri, 14 Jul 2000 16:00:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/changing-nis-domain-name/m-p/2430832#M2979</guid>
      <dc:creator>Antoanetta Naghiu</dc:creator>
      <dc:date>2000-07-14T16:00:05Z</dc:date>
    </item>
    <item>
      <title>Re: Changing NIS domain name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/changing-nis-domain-name/m-p/2430833#M2980</link>
      <description>That is a good point.  Try repushing all mapes (just issue ypmake from the master).  I don't know why that would be necessary, but see what happens.&lt;BR /&gt;&lt;BR /&gt;One last thing -- check /etc/passwd on the server to make sure the last line correctly refers login checks to NIS.</description>
      <pubDate>Fri, 14 Jul 2000 17:13:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/changing-nis-domain-name/m-p/2430833#M2980</guid>
      <dc:creator>Alan Riggs</dc:creator>
      <dc:date>2000-07-14T17:13:00Z</dc:date>
    </item>
    <item>
      <title>Re: Changing NIS domain name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/changing-nis-domain-name/m-p/2430834#M2981</link>
      <description>Thanks for the replies.&lt;BR /&gt;&lt;BR /&gt;Tried that (nis.client stop/start, yppush) and also made the machine to bind to the master using ypset.  /etc/passwd file has correct entry and also played with nsswitch.conf file to no avail (currently has compat in passwd line).</description>
      <pubDate>Mon, 17 Jul 2000 07:34:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/changing-nis-domain-name/m-p/2430834#M2981</guid>
      <dc:creator>Huiqi Liu</dc:creator>
      <dc:date>2000-07-17T07:34:22Z</dc:date>
    </item>
  </channel>
</rss>

