Sponsored Content
Operating Systems AIX Problem in Emailing all .sh_history entries Post 302741661 by MichaelFelt on Sunday 9th of December 2012 06:15:23 PM
Old 12-09-2012
I haven't looked at .should_history in a long time. It was text on AIX but might be binary now.
Have you tried using
$ history | mail ...
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to create .sh_history file

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

.sh_history contains the list of past commands

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 Advanced & Expert Users

.sh_history file

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

4. UNIX for Dummies Questions & Answers

Clarification on .cshrc,.exrc,.login,.profile,.sh_history files

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

5. AIX

history .sh_history sh_history

hi what's the difference between .sh_history and sh_history for root user? thanks itik (1 Reply)
Discussion started by: itik
1 Replies

6. AIX

timestamp in .sh_history using ksh shell

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

7. UNIX for Advanced & Expert Users

Incoherence between finger and .sh_history

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

8. AIX

Looking at .sh_history file.

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

9. UNIX for Advanced & Expert Users

sh_history file

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

10. Shell Programming and Scripting

Need help on conditional emailing

Hi All, The following databse table maintains VENDOR and EMAIL details. VENOR_NAME VENDOR_EMAIL DELL surendra@dell.com HP rajkamal@hp.com ACER sumathi@acer.com NOKIA kunal@nokia.com SONY sinu@sony.com We have to find emaild id of a vendor based... (7 Replies)
Discussion started by: ROCK_PLSQL
7 Replies
EXPIRE(8)						      System Manager's Manual							 EXPIRE(8)

NAME
expire - Usenet article and history expiration program SYNOPSIS
expire [ -d dir ] [ -e ] [ -f file ] [ -g file ] [ -h file ] [ -i ] [ -l ] [ -n ] [ -p ] [ -q ] [ -r reason ] [ -s ] [ -t ] [ -v level ] [ -w number ] [ -x ] [ -z file ] [ expire.ctl ] DESCRIPTION
Expire scans the history(5) text file /var/lib/news/history and uses the information recorded in it to purge old news articles. OPTIONS
-d If the ``-d'' flag is used, then the new history file and database is created in the specified directory, dir. This is useful when the filesystem does not have sufficient space to hold both the old and new history files. When this flag is used, expire leaves the server paused and creates a zero-length file named after the new history file, with an extension of ``.done'' to indicate that it has successfully completed the expiration. The calling script should install the new history file and un-pause the server. The ``-r'' flag should be used with this flag. -e If the ``-e'' flag is used, then as soon as the first cross posting of the article expires, all copies of it are removed. -f To specify an alternate history file, use the ``-f'' flag. -g If the ``-g'' flag is given, then a one-line summary equivalent to the output of ``-v1'' and preceeded by the current time, will be appended to the specified file. -h To specify an alternate input text history file, use the ``-h'' flag. Expire uses the old dbz(3z) database to determine the size of the new one. -i To ignore the old database, use the ``-i'' flag. -l Expire normally just unlinks each file if it should be expired. If the ``-l'' flag is used, then all articles after the first one are treated as if they could be symbolic links to the first one. In this case, the first article will not be removed as long as any other cross-posts of the article remain. -n If innd is not running, use the ``-n'' flag and expire will not send the ``pause'' or ``go'' commands. (For more details on the commands, see ctlinnd(8)). Note that expire only needs exclusive access for a very short time -- long enough to see if any new articles arrived since it first hit the end of the file, and to rename the new files to the working files. -p Expire makes its decisions on the time the article arrived, as found in the history file. This means articles are often kept a lit- tle longer than with other expiration programs that base their decisions on the article's posting date. To use the article's post- ing date, use the ``-p'' flag. -q Expire normally complains about articles that are posted to newsgroups not mentioned in the active file. To suppress this action, use the ``-q'' flag. -r Expire normally sends a ``pause'' command to the local innd(8) daemon when it needs exclusive access to the history file, using the string ``Expiring'' as the reason. To give a different reason, use the ``-r'' flag. The process ID will be appended to the reason. When expire is finished and the new history file is ready, it sends a ``go'' command. -s If the ``-s'' flag is used, then expire will print a summary when it exits showing the approximate number of kilobytes used by all deleted articles. -t If the ``-t'' flag is used, then expire will generate a list of the files that should be removed on its standard output, and the new history file will be left in history.n and history.n.dir and history.n.pag. This flag be useful for debugging when used with the ``-n'' and ``-s'' flags. Note that if the ``-f'' flag is used, then the name specified with that flag will be used instead of his- tory. -v The ``-v'' flag is used to increase the verbosity of the program, generating messages to standard output. The level should be a number, where higher numbers result in more output. Level one will print totals of the various actions done (not valid if a new history file is not written), level two will print report on each individual file, while level five results in more than one line of output for every line processed. -w Use the ``-w'' flag to ``warp'' time so that expire thinks it is running at some time other then the current time. The value should be a signed floating point number of the number of days to use as the offset. -x If the ``-x'' flag is used, then expire will not create any new history files. This is most useful when combined with the ``-n'', ``-s'', and ``-t'' flags to see how different expiration policies would change the amount of disk space used. -z If the ``-z'' flag is used, then articles are not removed, but their names are appended to the specified file. See the description of expirerm in news.daily(8). If a filename is specified, it is taken as the control file and parsed according to the rules in expire.ctl(5). A single dash (``-'') may be used to read the file from standard input. If no file is specified, the file /etc/news/expire.ctl is read. HISTORY
Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews. This is revision 1.19, dated 1996/10/29. SEE ALSO
ctlinnd(8), dbz(3z), expire.ctl(5), history(5), innd(8), inndcomm(3). EXPIRE(8)
All times are GMT -4. The time now is 06:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy