Greetings,

we have 85 Solaris 8 machines (spark) divided in
2 domains. Managment decided to move all hosts to
one domain without affecting the users.
After moving 15 machines, I noticed 6 of them are
generating repeated errors:

Jul 22 16:40:08 obsidian ypbind[4606]: [ID 379326 daemon.error]
service not installed, use /usr/sbin/ypinit -c


This is how I moved machines to the other domain
1- added the name of YP servers to /etc/hosts
2- kill ypbind
3- rm -r /var/yp/binding/tnt (old domainname)
4- remove tnt from the /var/yp/aliases file
5- domainname ndmz( new domain name)
6- ypinit -c
7- /usr/lib/netsvc/yp/ypbind

Truss showed that the system is still looking at old domain
/var/yp/binding/tnt for some reason.. Rebooting the machine
fixes that, but it's not an option.

Thank you,
-sm

Barry Margolin <barry.margolin@level3.com> wrote in message news:<wbcUa.393$0z4.80@news.level3.com>...
> In article <a365c2aa.0307250724.4c19ec74@posting.google.com >,
> Shawn Melnic <sham_x30@yahoo.com> wrote:
> >This is how I moved machines to the other domain
> >1- added the name of YP servers to /etc/hosts
> >2- kill ypbind
> >3- rm -r /var/yp/binding/tnt (old domainname)
> >4- remove tnt from the /var/yp/aliases file
> >5- domainname ndmz( new domain name)
> >6- ypinit -c
> >7- /usr/lib/netsvc/yp/ypbind
>
> From the domainname man page:
>
> The domain name of
> the machine is usually set during boot-time through the
> domainname command in the /etc/init.d/inetinit file. If the
> new domain name is not saved in the /etc/defaultdomain file,
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> the machine will revert back to the old domain after reboot-
> ing.

Thanks, but I did that ( domainname ndmz) that's what the ineinit
script does..
Why some machine had no problem with I changed the domainname and other
did? Is it possible to change it without reboot?

-sm

In article <a365c2aa.0307271857.b8540aa@posting.google.com> ,
Shawn Melnic <sham_x30@yahoo.com> wrote:
>Barry Margolin <barry.margolin@level3.com> wrote in message
>news:<wbcUa.393$0z4.80@news.level3.com>...
>> In article <a365c2aa.0307250724.4c19ec74@posting.google.com >,
>> Shawn Melnic <sham_x30@yahoo.com> wrote:
>> >This is how I moved machines to the other domain
>> >1- added the name of YP servers to /etc/hosts
>> >2- kill ypbind
>> >3- rm -r /var/yp/binding/tnt (old domainname)
>> >4- remove tnt from the /var/yp/aliases file
>> >5- domainname ndmz( new domain name)
>> >6- ypinit -c
>> >7- /usr/lib/netsvc/yp/ypbind
>>
>> From the domainname man page:
>>
>> The domain name of
>> the machine is usually set during boot-time through the
>> domainname command in the /etc/init.d/inetinit file. If the
>> new domain name is not saved in the /etc/defaultdomain file,
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> the machine will revert back to the old domain after reboot-
>> ing.
>
>Thanks, but I did that ( domainname ndmz) that's what the ineinit
>script does..

Running the domainname command does *not* update the /etc/defaultdomain
file. The inetinit script reads this file to determine the parameter it
should supply to the command during boot-time. You have to edit the file
manually.

>Why some machine had no problem with I changed the domainname and other
>did? Is it possible to change it without reboot?

Maybe the other machines haven't been rebooted, so they didn't revert.

You need to run "domainname" to change it for the current boot, and edit
/etc/defaultdomain to change it for future reboots.

--
Barry Margolin, barry.margolin@level3.com
Level(3), Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.