Date: Wed Jun 11 1997 - 06:16:51 CDT

My original question was :

Dear Sun-Managers,

I am administrator at a Solaris computer-system. Now, with all servers up and
running we are trying to change the actual searchpaths so we can move the target
directory (at which the searchpath points) [main directory] to another one. The
problem is that all of those links we made in the target directory are to be
changed too, as we are rebuilding our whole file-system.

Is there a possibility ( a tool / description ) to make these changes without
shutting down the servers ?

The answers were :

1. install the new directory with all files
2. edit your your searchpath: in minimum put the new path in front of the old
3. the users have to logout and login again to activate the new path.

It should not be necessary to shutdown the system.
Looking for some tools, you will find :#

Now for the question :
I have to install some new programs on our serves and workstations. Due to
this i have to edit the startup and login scripts. Is there a way
(tool,script...etc) to automate this ?

By the way, can anyone tell me where to find admin tools for servers and
workstations (Excuse me, but I am new on this list)

Let the users execute the command :
  source ~/.cshrc

after you changed the paths in the .cshrc file for each user
If all of the login files were the same on all workstations you could create
a master file and rcp the file out to all of the workstations, and then the
same for the servers, of course this is depending on whether or not the file
is the same for each workstation and server.

It is possible to export the .cshrc and .login files. This would be another
possible solution and have all of the users mount specific .cshrc and so on.
You can create default login scripts for "all users" in different ways,
depending on hat OS you use. One way is to write a script that copies a
"standard" login shell rc file when you create the user's account.

Another is to edit the master default login script(s) so that the
"standard" information becomes available to all users the moment they
login, before their personal login scripts run.

Another way to handle it is to create a script library, and include the
script library path in the default login script, then including the
names of individual scripts in the individual login scripts in an
as-needed basis.

There are probably a dozen ways to do that. Probably several dozen
"utilities" to help you do it.

If you're using Solaris, just log in as root (or superuser) and enter
the command "admintool". There are more advanced tools in the Soltice
Admin Suite (an add-on pkg for Solaris from Sun).

Solstice Admin Suite is included with the Server software bundle, but
you have to install it specifically. It's not a default.

If you're using SunOS, it's best to get a copy of the System
Adminstrator's Handbook from O'Rielly and Associates. It's "the bible"
of system administration. As a new admin, it's a good idea to find or
buy a copy anyway. It's the cheapest tool you can get, and the most

You can get LOTS of help on the subject of the book and other
administrative books from O'Rielly, at their website: <=== This side is very interesting
For a collection of free BSD facilities try :
In Solaris, there is a directory called /etc/default

This is where system default information is kept.

This has a file called "login" which gets executed every time someone
logs into the machine. This has general system defaults, like the
original path statement for each login. This should NOT become the
login script for every user.

This should only be for system-wide standards. If you use this file for
all the things any user could want, then all users have access to them,
which makes it hard to do secure stuff.

On the other hand, there is also a "default login scripts" setup that
will create default login scripts for the users when you create their
accounts. You probably have to create the files yourself.

The usual location of the directory for these scripts is /etc/skel (for

In this directory, you can create a default .login .profile .csh .bash
..bashrc .kshrc .tcshrc (etc).

If you place all the default files in this location, then ehen you
create a new user with the bash shell, you copy the .login .bash .bashrc
files to that home directory after you create it, then cd to that home
directory and chown them to that user.

For Bourne, just copy the .profile

For C Shell, just the .login and .cshrc

For Korn, .profile and .kshrc (maybe a .env)

Of course, each rc file must be scripted in the correct language or they
won't work.

You can write a script for each "flavor" of shell that copies the
correct files to the user and chowns them to the user with one command,
which will save you lots of time.

Solaris has a /etc/skel by default with 3 sample scripts for .login,
..cshrc, and .profile.

These answers are in the order I received them. Sorry for beeing late ,but I was
ill and then had to work around with the answers.

A multitude of thanks to those who responded ! Our systems are running fine

                Jim Harmon
                Mark Phillips
                Matthew Stier
                Charity Gustine
                Adrian Koenig
                Stefan Voss (thanks for your outstanding performance)

(no order)

Thanks again, and keep the good work up !

Juergen Schultz
Stud. cand. Diplominformatiker (FH)

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:56 CDT