08-21-2001
Yes, I know it has different name comes with different shell. My question is how this file was created? I have to manually create it or it was created when I create the user's account? Because in one machine I saw this file under my directory in another machine it doesn't exist. It should have some place to make this happen(define in a system file?)
My another question is: Is it possible to check the user's history if the user doesn't have a history file? where can I go to check?
Thanks!
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi, .sh_history keeps a list of past commands that we entered. but it has a limit and where do we set this limit. thanks. (1 Reply)
Discussion started by: yls177
1 Replies
2. UNIX for Advanced & Expert Users
Hi Friends,
We are currently 5 people using same Unix login-id on different terminals, .sh_history file contains list of commands typed by all 5 peoples(commands history) with the below list :
$tail .sh_history
ls -ltr
pwd
cd ..
ls -ltr
clear
cd temp
more kk.lst
Now my question... (9 Replies)
Discussion started by: krishna
9 Replies
3. UNIX for Dummies Questions & Answers
All,
I had a request to delete filed under a directory that was 35 days old . And they asked me to scedule it in CRON . I have done that .
I have use find and delete with mtime to perfrom this task .
But my script is not deleting this .cshrc,.exrc,.login,.profile,.sh_history file... (1 Reply)
Discussion started by: arunkumar_mca
1 Replies
4. AIX
hi
what's the difference between .sh_history and sh_history for root user?
thanks
itik (1 Reply)
Discussion started by: itik
1 Replies
5. AIX
Hello Everyone:
Does anyone know how I will setup my account to put timestamp in my .sh_history? I do not hold the root account. I am using AIX 5 and ksh shell. I tried every solution I can find in the internet but nothing seems to work OR I am just applying those in the wrong way. Anyone knows... (4 Replies)
Discussion started by: Orbix
4 Replies
6. UNIX for Advanced & Expert Users
Hello,
I've a script that verifies users connections.
This is the check part
do
NEVER=$(finger $USER | grep -i Never)
if
then
NAME=$(finger $USER | grep -i "In real life" | sed -e 's/^.*life: //')
echo $USER $NAME >> never_logged #" "$NEVER
fi
done
that for a specific... (6 Replies)
Discussion started by: gogol_bordello
6 Replies
7. AIX
I reviewed a couple old post where shockneck posted the use of the EXTENDED_HISTORY=ON variable to place a timestamp in the .sh_history file when using ksh and using the fc -t command to read the .sh_history file.
The fc command reads my history file. As an admin I would like to be able to read... (5 Replies)
Discussion started by: juredd1
5 Replies
8. UNIX for Advanced & Expert Users
Hi,
I'm on a linux machine. But I see that sh_history is not updated since february 15. How is it possible ?
Thank you.
uname -a
Linux MYSERVER 2.6.18-194.11.3.el5PAE #1 SMP Mon Aug 23 15:57:10 EDT 2010 i686 i686 i386 GNU/Linux
ls -al
-rw------- 1 oracle dba 3644 fév 15 09:28... (10 Replies)
Discussion started by: big123456
10 Replies
9. AIX
Hi,
I can't get all the enties of AIX .sh_history in email. only first entry of the history is emailed after executing the below code.
mail -s "History `date +%d-%m-%Y`" myemail@xyz.com <$HOME/.sh_history
Can anyone help? (3 Replies)
Discussion started by: m_raheelahmed
3 Replies
LEARN ABOUT REDHAT
passwd
PASSWD(5) File formats PASSWD(5)
NAME
passwd - password file
DESCRIPTION
Passwd is a text file, that contains a list of the system's accounts, giving for each account some useful information like user ID, group
ID, home directory, shell, etc. Often, it also contains the encrypted passwords for each account. It should have general read permission
(many utilities, like ls(1) use it to map user IDs to user names), but write access only for the superuser.
In the good old days there was no great problem with this general read permission. Everybody could read the encrypted passwords, but the
hardware was too slow to crack a well-chosen password, and moreover, the basic assumption used to be that of a friendly user-community.
These days many people run some version of the shadow password suite, where /etc/passwd has *'s instead of encrypted passwords, and the
encrypted passwords are in /etc/shadow which is readable by the superuser only.
Regardless of whether shadow passwords are used, many sysadmins use a star in the encrypted password field to make sure that this user can
not authenticate him- or herself using a password. (But see the Notes below.)
If you create a new login, first put a star in the password field, then use passwd(1) to set it.
There is one entry per line, and each line has the format:
account:password:UID:GID:GECOS:directory:shell
The field descriptions are:
account the name of the user on the system. It should not contain capital letters.
password the encrypted user password or a star.
UID the numerical user ID.
GID the numerical primary group ID for this user.
GECOS This field is optional and only used for informational purposes. Usually, it contains the full user name. GECOS means
General Electric Comprehensive Operating System, which has been renamed to GCOS when GE's large systems division was sold
to Honeywell. Dennis Ritchie has reported: "Sometimes we sent printer output or batch jobs to the GCOS machine. The gcos
field in the password file was a place to stash the information for the $IDENTcard. Not elegant."
directory the user's $HOME directory.
shell the program to run at login (if empty, use /bin/sh). If set to a non-existing executable, the user will be unable to
login through login(1).
NOTE
If you want to create user groups, their GIDs must be equal and there must be an entry in /etc/group, or no group will exist.
If the encrypted password is set to a star, the user will be unable to login using login(1), but may still login using rlogin(1), run
existing processes and initiate new ones through rsh(1), cron(1), at(1), or mail filters, etc. Trying to lock an account by simply chang-
ing the shell field yields the same result and additionally allows the use of su(1).
FILES
/etc/passwd
SEE ALSO
passwd(1), login(1), su(1), group(5), shadow(5)
1998-01-05 PASSWD(5)