We have a system set up for staticly building files for groups of hosts
based on hostname, architecture, and/or revision.
The user .cshrc files are very simple, simply doing 'source's of several
files, the main system .cshrc, their own personal .cshrc called
.usercshrc and a personal host specific cshrc .usercshrc.hostname
You should be able to take a look at:
/afs/umr.edu/software/proftree/profiles/
Or I can make a copy for you.
Of course, this also ties in with our common source code trees. We
automatically build symlink trees for each architecture so that
/umr/bin/elm automatically points to the correct one on each host... That
is also automatic.
We currently only do .cshrc, .profile, and .login, but it could easily be
extended to handle other files.
-- Nathan
> Now we have common login and common password facilities for our users,
> I expect them to come hammering on my door for common login procedures.
> Which I now made my little? dot-files project.
>
> In my fantasy it should be one single source somewhere in afs, called
> bby the users which does the right thing for the sort of dot-file it
> is, the platform it runs on and the particular config.
> So what it roughly should cover is:
> .profile, .login,.logout,.cshrc, kshrc,.xinitrc,xserverrc,xsession
> (more would be too over ambitious)
>
> my question this early friday morning is
>
> HELP HELP HELP
>
> Does anybody have expereince with this. Any Do-s or Don't-s?
>
> My users would highly appreciate you input to this as well as I.
>
> Joop Verdoes
> Shell International Production and Exploration
> Rijswijk, the Netherlands
>
------------------------------------------------------------
Nathan Neulinger Univ. of Missouri - Rolla
EMail: [EMAIL PROTECTED] Computer Center
WWW: http://www.umr.edu/~nneul SysAdmin: rollanet.org
