by In an article I asked, if it was posible to terminate further execution
of BOTH an .cshrc-file AND a global /etc/csh.cshrc-file implemented
by putting this line into every users .cshrc-file:
source /etc/csh.cshrc
The problem was, that putting an exit into /etc/csh.cshrc only
terminated the source of this file and not the source of the users
own .cshrc-file.
possible, because csh isn't set up to permit changes in it's execution-
stack.
My real problem was that under some very special circumstances I didn't
want the user to perform the tset-command in his .cshrc-file. But as Tod
pointed out, it wasn't necessary to exit the source of .cshrc to achieve
this. Instead I could just put a wrapper around /usr/ucb/tset that only
calls the original tset-program when a special environment variable isn't
set.
.cshrc-files:
source /etc/csh.cshrc
if ($?leave_cshrc == 1) exit
Both solutions will ofcourse work, but in my situation the former is
more clean and reflects what I really wanted to achieve.
Bonde
--
Systemadministrator, Datakontoret, Aarhus University
Phone : +45 86 20 27 11 ext. 4993
Monday : 10-12
Tuesday : 12-14
Wednesday : 12-14
Thursday : 12-14
Friday : 10-11