.cshrc owned by ?

        Thanks to all those who replied to my original posting.

>

>

> Is there anyway to have the .cshrc owned by someone other than the

> user?

>

        The idea was to have the users .cshrc owned by root or an

        admin account. Having discovered that this is not possible

        we will now look into the ways to achieve the result.

        For those who are interested below are some off the

        responses/suggestions from the net. Generally it was either

        switch to tcsh or source a global .cshrc file from each

        users .cshrc.

In articlergl@mail.fwi.uva.nl,casper@fwi.uva.nl (Casper H.S. Dik) writes:

>mderu@fossa.navy.mil.nz (Mike deRuiter) writes:

>

> > Is there anyway to have the .cshrc owned by someone other than the

> > user?

>

> No. This is a security feature in the csh. (Prevents people with group/world

> writable home directories from getting a silly .cshrc. Why not do give

> all users a .cshrc that reads:

>

> source /the/global/Cshrc/file

>

> Casper

----------------------------------------------------

In article94Mar3110705@ab20.larc.nasa.gov,jason@ab20.larc.nasa.gov (Jason C. Austin) writes:

> In article <CM2F1z.Csx@dswe.navy.mil.nz>mderu@fossa.navy.mil.nz (Mike deRuiter) writes:

>

> ->

> -> Is there anyway to have the .cshrc owned by someone other than the

> -> user?

> ->

>

> You can get a copy of tcsh which has a global .cshrc feature

> along with a lot of other excellent features. Preventing users from

> modifying their own cshrc file like you are trying to do is a bad

> idea.

> --

> Jason C. Austin

>j.c.austin@larc.nasa.gov

>

-------------------------------------------------------------

>FromMichal.Jankowski@fuw.edu.pl Fri Mar 4 09:13:37 1994

Mike> We would like to have a default .cshrc file for all our users

Mike> to set up a few network wide aliases which users cannot

Mike> edit/accidentally delete. Users will have the opportunity to

Mike> customize their own .mycshrc

Switch to tcsh.

It has support for global .cshrc and .login (usually called

/etc/csh.cshrc and /etc/csh.login) built-in.

IMHO, tcsh is much superior to csh - command-line editing, filename

completion, visual stepping through history list, more and more.

  Michal

--------------------------------------------------------------

>Fromamos%europa@europa.acs.unt.edu Tue Mar 8 12:11:10 1994

    Mike> We would like to have a default .cshrc file for all our users to set

    Mike> up a few network wide aliases which users cannot edit/accidentally

    Mike> delete. Users will have the opportunity to customize their own

    Mike> .mycshrc

You may have already received this suggestion, but have you looked into

tcsh? Tcsh is a csh compatible shell that reads the following upon

startup:

    1. /etc/csh.cshrc (global .cshrc)

    2. /etc/csh.login (global .login; for login shells only)

    3. ~/.tcshrc (user shell setup)

    4. ~/.cshrc (only if ~/.tcshrc wasn't found)

    5. ~/.login (for login shells only)

This is what we're using and have been very pleased with the results.

Tcsh also allows using the arrow keys for command line editing, which

is much nicer for our users coming from the VMS environment.

Amos

Lt Mike de Ruiter Smail: TSG Building

mderu@fossa.navy.mil.nz Naval Base

                                 \\\\\// Private Bag 32901

Ph :+64 9 4455809 | | Auckland

Fax:+64 9 4455475 (.) (.) NEW ZEALAND

============================oOO====(_)====OOo================================

No employer is allowed to have the opinions I have and therefore are

not

responsible for them.

=============================================================================

[6790 byte] By [CodeProf.com] at [2007-12-25 8:42:00]