Thank you all who respond. The responses were along the lines of...
tcsh /etc/csh.login
csh /etc/csh.login
sh /etc/profile
others suggest looking at the man pages for the specific shell.
I might need the file that prints the /etc/motd file... <hmmmm>
To the person that responded rtfm it would be helpful if you suggested what
f'in manual I should read. I am new to unix and my background is rsts and
vms the documentation is quite different in the two camps. I still have not
figured out how a PostScript programming manual will help in unix
administration but that is a topic for another question.
I was disappointed to find that unix did not have a "master" sylogin.com.
Then I began to realize that I might need a different approach to what I
needed to do.
We have a user that has some major privileges to do things on the system.
I was asked by management to set up a log file on this user.
In VMS the sylogin.com first checks to see if any user that logs onto the
system has a special process right that we add to VMS accounts that need a
logfile on them. If the user has this process right (the right to be
logfiled?) then sylogin.com gives a "password error";
set host f$getsyi("NODENAME") /log = `f$getjpi("","PID") + ".log"'
and every thing that is on the users screen or batch job is logged to a file.
The user just has this "problem" of never being able to key there password
right the first time -- or so they think.
This logfile is turned on or off by the VMS authorize grant /id and
revoke /id commands.
I've tried to do this same thing with unix's script command, but
1) it prints/echoes that the script files name and path (giving
the user a warning that they are being logfiled)
2) kicks them out of the start up procedure in a different shell and
in a different directory.
3) losses/replaces some environmental variables.
4) completes the login script after the user dose a ^D to logoff.
After checking the user name I've tried doing a
ksh | tee -ai `date +%a%d%b%Y`/`date +%H%m`
that solves the problem of staring the wrong shell but commands like ls
work funny(er).
anyone have better (more stealth) options?
digital support suggested turning accounting on, and added that there would
be performance hits and I would only see the system calls and not the screens.
I don't need to capture x-window displays only the i/o stream going to/from
the dumb terminal. I am hoping that I can just do a cat on the log file and
be able to "run" and see the screens/commands that the user was in.
A real time solution, seeing/watching the user as they are doing there thing
would also be kwel too; managers could watch and just do a script on themselves.
Thank you again for your time
+--------------------------+------------------------------------------------+
|H. Blakely Williford | When I was a boy I was told that anybody could |
|Systems Administrator | become President; I'm beginning to believe it. |
|The Fuller Brush Company | - Clarence Darrow |
+--------------------------+------------------------------------------------+
Received on Fri May 24 1996 - 18:10:52 NZST