Sponsored Content
Top Forums UNIX for Advanced & Expert Users History to Another file [local user history , but root access] Post 302551572 by linuxadmin on Wednesday 31st of August 2011 02:13:37 AM
Old 08-31-2011
History to Another file [local user history , but root access]

Hi all,

My need is :
1. To know who , when , which command used.
2. Local user should not delete this information.
[The thing is , here we have a number of employees working in root permission.!!! And we are not actually getting who is doing which command and all...]

I mean , with an example , i can say
i have a user user1

i need to give all the following permissions to user1, :
a. A specific directory other than his home directory.
b. To edit /etc/profile
c. And/Or any other specific files/dirs.

user1's history will be saved in ~/.bash_history
user1 will have -rw-------. permission to ~/.bash_history

So there is a chance that he may delete the file itself / delete the content.

And so , i am thinking to do like..
i will have another file somewhere , say , /var/.bash_hist_user1

so automatically , What are all the commands entering by user1 should come inside /var/.bash_hist_user1 also.

OR ELSE


What are all the commands entering by user1 will come in ~/.bash_history
But he cannot delete the file / content.



Is it possible ? Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How to access all user history file

Team , using fc command we can get details of our history file .. Is it possible to get the same result for different user from root.. Actually I need to collect all the stuff from select users history file for day to day basis. thanks in advance .. (2 Replies)
Discussion started by: rgpai9972
2 Replies

2. Shell Programming and Scripting

access user history as root

Hi, I need to access a user's command history. However, the dilemma is that he is logged in and so his current history is not yet flushed to .bash_history file which gets flushed when he logs out. Is there a way I can still access his most recent history? thank you, S (4 Replies)
Discussion started by: sardare
4 Replies

3. UNIX for Dummies Questions & Answers

How to review the history and the commands that has been done in this history?

Hello every body, Kindly inform me How Do i find out the time I executed a command previously on UNIX Solaris?? To be more specific and more clear about what i want to know is that I want a command the enables me to know the history and which command i run at this history/time. FYI I used... (5 Replies)
Discussion started by: ahmedamer12
5 Replies

4. Shell Programming and Scripting

Temporary command history on local machine

Hey guyz, I'm trying to get the command history for my active users sessions on the local machine and i kinda hit a tough wall Is command-line history for my current user saved somewhere else besides $HOME/.bash_history? I have been told that there is some temporary file stored on the local... (2 Replies)
Discussion started by: mishu_cgm
2 Replies

5. UNIX for Dummies Questions & Answers

History to Another file [local user history , but root access]

Hi all, My need is : 1. To know who , when , which command used. 2. Local user should not delete this information. I mean , with an example , i can say i have a user user1 i need to give all the following permissions to user1, : a. A specific directory other than his home... (1 Reply)
Discussion started by: sriky86
1 Replies

6. Red Hat

How to check local accounts have root and user access rights ?

Hi, I have three servers,For 3 servers how i can take output,all the local accounts and details of whether the access is Root or User access. cheers (1 Reply)
Discussion started by: ranjithm
1 Replies

7. Shell Programming and Scripting

History of all the users in single file with command , date . time , ip and user

HTML Code archive_history() { HISTORYOLD=${HISTFILE}.archive CURTIME=`date` CURTTY=`tty` IP=$(echo $SSH_CLIENT | awk '{print $1}') if ; then echo "#-${HOSTNAME}-- ${CURBASHDATE} - ${CURTIME} ($CURTTY) ${USER} ${IP}----" >> $HISTORYOLD history... (2 Replies)
Discussion started by: rehantayyab82
2 Replies

8. Shell Programming and Scripting

History of all the users in single file with command , date . time , ip and user

HTML Code: archive_history() { HISTORYOLD=${HISTFILE}.archive CURTIME=`date` CURTTY=`tty` IP=$(echo $SSH_CLIENT | awk '{print $1}') if ; then echo "#-${HOSTNAME}-- ${CURBASHDATE} - ${CURTIME} ($CURTTY) ${USER} ${IP}----" >> $HISTORYOLD history... (0 Replies)
Discussion started by: rehantayyab82
0 Replies

9. Shell Programming and Scripting

On korn shell, how to share history between regular user and root?

I'm exploring OpenBSD and want to stick to its default shell, which is ksh. My goal is for my regular user ("bruno") and root user to have a shared history file. However, it seems that when running as root, ksh refuses to write to a HISTFILE that is owned by non-root user. This illustrates the... (3 Replies)
Discussion started by: DevuanFan
3 Replies

10. What is on Your Mind?

The Great History of UNIX (1969-1999) | 30 Years of UNIX History | YouTube Video

I am pleased to announce this new video in 1080 HD for UNIX lovers honoring thirty years of UNIX history spanning from 1969 to 1999 presented in 150 seconds (two and a half minutes) in 1080 HD, celebrating the 50th anniversary of UNIX. The Great History of UNIX (1969-1999) | 30 Years of UNIX... (8 Replies)
Discussion started by: Neo
8 Replies
talk(1) 						      General Commands Manual							   talk(1)

Name
       talk, otalk - talk to another user

Syntax
       talk person [ttyname]

       otalk person [ttyname]

Description
       The command is a visual communication program which copies lines from your terminal to that of another user.

       If  you	wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on another
       host, then person is of the form :
       host!user
	or
       host.user
	or
       host:user
	or
       user@host
       The form user@host is perhaps preferred.

       If you want to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal name.

       When first called, it sends the message
       Message from TalkDaemon@his_machine...
       talk: connection requested by your_name@your_machine.
       talk: respond with: talk your_name@your_machine

       to the user you wish to talk to. At this point, the recipient of the message should reply by typing
       talk  your_name@your_machine

       It doesn't matter from which machine the recipient replies, as long as his login-name is the same.  Once communication is established,  the
       two parties may type simultaneously, with their output appearing in separate windows.  Typing Ctrl-L will cause the screen to be reprinted,
       while your erase, kill, and word kill characters will work in talk as normal.  To exit, just type your interrupt character; then moves  the
       cursor to the bottom of the screen and restores the terminal.

       Permission to talk may be denied or granted by use of the mesg command.	At the outset talking is allowed.  Certain commands, in particular
       and disallow messages in order to prevent messy output.

       In order to use the program with machines on your network that may be running earlier versions of ULTRIX, you must initiate a session  with
       the  command (/usr/ucb/otalk) instead of the command You must also respond to a request from a machine running an older version of the pro-
       gram with the command. See the Restrictions section.

Examples
       The following example demonstrates how to use the command.  In this case, user1, whose system (system1) is running ULTRIX V2.2 initiates  a
       session with user2, whose system (system2) is running ULTRIX V3.0.  User1 types the following:
       system1> talk user2@system2
       The following message appears on the screen of user2:
       Message from Talk_Daemon@system2 at 12:37 ...
       talk: connection requested by user1@system1.
       talk: respond with:  otalk user1@system1
       To establish the connection user2 follows the instructions from the Talk_Daemon and types the following at the system prompt:
       system2> otalk user1@system1

Restrictions
       The  version  of  released  with ULTRIX V3.0 uses a protocol that is incompatible with the protocol used in earlier versions. Starting with
       ULTRIX V3.0, the program communicates with other machines running ULTRIX, V3.0 (and later), and machines running 4.3  BSD  or  versions	of
       UNIX based on 4.3 BSD.

       The command is not 8-bit clean. Typing in DEC Multinational Characters (DECMCS) causes the characters to echo as a sequence of a carets (^)
       followed by the character represented with its high bit cleared. This limitation makes unusable if you want to communicate using a language
       which has DECMCS characters in its alphabet.

Files
       to find the recipient's machine

       to find the recipient's tty

See Also
       mail(1), mesg(1), who(1), write(1), talkd(8c)

																	   talk(1)
All times are GMT -4. The time now is 06:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy