04-07-2003
Thanks for your reply, but the file wtmp (or wtmpx) is not in readable format !!! is there any alternative solution, but we strictly use the same login-id for 5 people(dept. login-id).
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Thanks PxT answered my "compare two files"question very quick and neat!!:-)
I have a question about .history file I couldn't find any satisfied answer from book.
1. This file was created automatically when you set up user's environment or you have to use a command to create it or you... (4 Replies)
Discussion started by: b5fnpct
4 Replies
2. 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
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
10. Shell Programming and Scripting
Shell script logic
Hi
I have 2 input files like with file 1 content as (file1)
"BRGTEST-242" a.txt "BRGTEST-240" a.txt "BRGTEST-219" e.txt
File 2 contents as fle(2)
"BRGTEST-244" a.txt "BRGTEST-244" b.txt "BRGTEST-231" c.txt "BRGTEST-231" d.txt "BRGTEST-221" e.txt
I want to get... (22 Replies)
Discussion started by: pottic
22 Replies
LEARN ABOUT OSF1
devassign
devassign(4) Kernel Interfaces Manual devassign(4)
NAME
devassign - Device assignment database file (Enhanced Security)
DESCRIPTION
The system supports a single device assignment database that contains entries for login terminals and X terminals. Authentication programs
use information in the device assignment database to determine if a login is permitted on the terminal. Information from the terminal con-
trol database, /etc/auth/system/ttys.db, can also affect terminal login permissions.
A device assignment database entry consists of keyword field identifiers and values for those fields. If a necessary value is not speci-
fied in an entry, a default value for the field is supplied from the system default file, /etc/auth/system/default. The edauth utility is
used to alter device assignment database entries.
The format of the terminal control database file is identical to other system authentication database files and is described in the auth-
cap(4) reference page. The following keyword identifiers are supported: The identifier in this field specifies a comma-separated list of
aliases that refer to the same device defined by the entry. Use of this field avoids the need to replicate device assignment database
entries for all device aliases. This field is ignored if it is set in a template or in the default database. This field specifies the
device that is described by the entry. Device types supported include: The device is assigned as a local login terminal device. The X
windows display entry for handling graphics heads or X terminals.
This field is ignored if it is set in a template or in the default database. This field, if specified, contains a comma-separated list of
user names that are permitted to use the device for login or the import and export of data. If the list is not present, all users are per-
mitted to use the device. If the list is present, it is searched for a match by the login program to determine if the user is permitted to
use the device.
This field is ignored if it is set in a template or in the default database.
EXAMPLES
The following example shows a device assignment database entry for a terminal device with a list of allowed users: tty0:v_devs=/dev/tty0:
:v_type=terminal:v_users=may,tdy,ssv,rgb: :chkent:
The following example shows a device assignment database entry for an X terminal device:
local:0|local:0.0:v_devs=local:0,local:0.0:v_type=xdisplay:chkent:
FILES
Specifies the pathname of the file.
RELATED INFORMATION
Commands: cpio(1), login(1), tar(1), edauth(8)
Functions: getdvagent(3)
Files: authcap(4), default(4), ttys(4) delim off
devassign(4)