SUMMARY: rc.local

Thanks to all who replied with so many different answers!  It really helps to 
have a lot to look and and try to get things just right.

It was a general consensus that what is/was rc.local in Linux is V5 using the 
/etc/rc* directory start|stop scripts.  S for start and K for stop.   I've 
been out of the unix world for about a year and a half and didn't realize that 
rc.local is seldom used in Linux anymore as well.  Thanks for all the advice.

As for those who asked me about using a Microsoft Service for Unix (SFU) on 
Windows 2000  Active directory.  I do have it working and it's working pretty 
well.  My problem with getting things running properly was that the W2K server 
had to be rebooted after SFU installation.

The W2K SFU server is also configured as an NIS master.  Initializing the 
client works the same as if the NIS master were a solaris machine.  You just 
have to make sure your /etc/hosts file reflects the hostname and IP address of 
the NIS master and that you are in the same domain.  My W2K NIS server resides 
in a different subnet and there's no problem as long as you have the 
/etc/defaultrouter set.

It works pretty slick by making all of the existing W2K users (I have around 
500). Instantly available to login to my Solaris workstations and it NFS maps 
their home directories to the W2K server so passwords are synchronized.

The draw backs:
1. NIS is less secure and will take some hoop jumping to close the holes.  
However, there is hope that SFU 3.0 will allow NIS+ configuration.  W2K is 
also Kerberos enabled so you can configure your security that way as well.

2. The default installation of Solaris allocates a large part of your disk 
space to /export/home and hard mounts the volume.  This causes problems when 
authenticating to W2K since it is trying to NFS mount home directories on 
/export/home .  You can either change this on your Solaris installation or 
change the setting in W2K to mount home directories somewhere else.

3.  This may effect using jumpstart since the W2K NIS server does not seem 
have a place to enter ethers info.  I'm not sure at this point if that's 
what's causing my jumpstart problems or not.

Thanks again for all the advice,
Jim


-----Original Message-----
             From: jdickert [jdickert@vt.edu]
             Sent: Monday, March 04, 2002 7:56 AM
             To: sunmanagers@sunmanagers.org
             Subject: rc.local


             Is there an equivalent to the Linux rc.local file for auto 
starting daemons on Solaris 8. I'm new to Solaris and it seems most that is 
written on configuring anything on a Unix system is written for Linux and very 
little about Solaris specific files.

             I'm really having this problem trying to get an NIS slave 
configured to a W2K/AD server running SFU for user authentication and home 
directory mapping. Any suggestions on this would be greatly appreciated as 
well.

             Any tips on testing that Solaris NIS clients are actually 
communicating with the W2K NIS master would be helpful as well. Several times 
now I have configured the client and it appears to be communicating but when I 
cp the nsswitch.nis file to
             nsswitch.conf and reboot the machine hangs when in waiting for 
the NIS services to start and I end up having to reinstall.

             Thanks for any help,
             Jim
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers