Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

we are 100% Linux user across the network and we do work round clock, what happens shift change next admin come to his shift on that time what all issues comes he get resolve the issues but they just clear history from terminal. If we want record every at terminal what they have done to resolve the same issues or we can monitor as well, for trouble ticket we have internal OTRS which they update for reporting.

Thanks ton

share|improve this question
add comment

4 Answers

up vote 3 down vote accepted

When I want to log a root session I use rootsh. If admins are required to use sudo for all commands, it will also log all commands.

You might take a look at screen too, as it might accomplish what you're attempting to do.

Ultimately, logging may not be the best situation for your workflow. Requiring a motd, wiki, or simple Web site to be updated for all changes may be better.

share|improve this answer
    
thanks tone gr8 –  neolix May 10 '10 at 19:12
add comment

Take a look at my history logging functions and see if they could be adapted to your needs.

This is what a couple of typical lines from my log file might look like:

echo hello ### user@host.tld Bash-4.0 /dev/pts/1 192.168.2.22 20100510 17:53 /home/user/test
cd .. ### user@host.tld Bash-4.0 /dev/pts/1 192.168.2.22 20100510 17:53 /home/user/test -> /home/user

The first line above includes a command, a comment marker, the user/host, shell version, terminal device and IP, the date and time and the directory that was current when the command was issued. The second line is an example of an entry that is produced when a cd command is used and the function's -t option is active. It shows the previous and new working directories.

To set that up:

  • Source the function
  • set the variable
    hcmntextra='date "+%Y%m%d %R"'
  • set the variable
    PROMPT_COMMAND='hcmnt -eityl ~/.hcmnt.log "$LOGNAME@$HOSTNAME Bash-${BASH_VERSION%.*}"'

Choose appropriate locations for files and add the steps above to your ~/.bashrc files.

The function takes several optional switches. One of interest may be -l. With it, commands are written to a log file. You can grep that file and copy and paste commands that you need to re-run. If you omit that switch, the annotated lines are instead written to the shell's history where they can be recalled and reused using the history manipulation features of Bash. The fact that the annotations follow a comment character means that you can re-use the commands as-is and the annotations will be ignored.

share|improve this answer
1  
Dennis your gr8 man thanks 1PB –  neolix May 11 '10 at 0:43
    
It sounds like they are wanting to monitor people who don't want to be monitored. If neolix uses your solution all the "evil" admins have to do is remove the setting from their environment. Not really much different than clearing the history –  ScottZ May 11 '10 at 6:31
    
@ScottZ: That's certainly a potential issue, but it's not the way a read the question. –  Dennis Williamson May 11 '10 at 8:00
add comment

Here's a manual option. Try the script command.

script -a ticketnum.txt then do what you need to do ctrl+d stops the recording and the resulting file can be attached to the ticket. I'm sure this can be automated a bit with some scripting.

share|improve this answer
add comment

You may be interested in something like shell_sink for recording and annotating your shell history.

share|improve this answer
    
thanks a ton i'm trying out if don't understood any thing i'll keep bothering thanks ton –  neolix May 10 '10 at 19:10
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.