Sponsored Content
Full Discussion: History
Top Forums Shell Programming and Scripting History Post 302197702 by ShawnMilo on Wednesday 21st of May 2008 12:54:14 PM
Old 05-21-2008
Quote:
Originally Posted by Vivek788
but hey let me ask..bash_logout doesn't execute when I close my terminal sessions does it?
The file old_commands.log has not yet been created.
It executes for me on logout. Are you sure you're using bash? Also, the filename should begin with a period: .bash_logout

It's not clear from your message how you have named it.

Shawn
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

History

hi there all , i would like to know what are the other alternatives besides .sh_history file to get all commands typed on console .. Can u help me ? Thanks for all PS : I'm a newbie on this forum :rolleyes: (2 Replies)
Discussion started by: JuniorJack
2 Replies

2. Shell Programming and Scripting

History ??

Hi, How can i see first 3 commands that are there in history {fc -l} ? Thanks (1 Reply)
Discussion started by: varungupta
1 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. UNIX for Advanced & Expert Users

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... (3 Replies)
Discussion started by: linuxadmin
3 Replies

5. UNIX for Dummies Questions & Answers

The history command: See other users command history

Can anyone tell this: If two users are logged into the same server from different locations. Is there a way to see the history command of the other user? I tried the history command, but it is showing me only the commands I used. Thanks in advance for your help. Iamnew2solaris (1 Reply)
Discussion started by: iamnew2solaris
1 Replies

6. AIX

history

Hi How to see all the commands typed as user padmin in the vio servers ? history command shows only a few commands ? (1 Reply)
Discussion started by: newtoaixos
1 Replies

7. 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

8. 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
CEREAL-ADMIN(8) 					      Administration Commands						   CEREAL-ADMIN(8)

NAME
cereal-admin - administer cereal sessions SYNOPSIS
cereal-admin command [args] DESCRIPTION
cereal-admin is a program to administer cereal sessions. A cereal session is a special (restricted) screen(1) session attached to a serial terminal. Each cereal session is owned by a particular user (USER) who is allowed to "attach" to the cereal screen session and interact with the specified serial terminal via screen. Each cereal session is also associated with a particular log group (LOGGROUP) whose members are allowed to "follow" the logs of the session. Cereal was designed to monitor serial lines connected to the serial consoles of remote machines. The cereal system is outlined at: http://cmrg.fifthhorseman.net/wiki/cereal SUBCOMMANDS
cereal-admin takes various subcommands: create SESSION TTY BAUD USER LOGGROUP Create a new session named SESSION on tty TTY, with baud rate BAUD. USER is the user that will own the session, and LOGGROUP is the group that will be able to follow the session non-interactively (ie. read the logs). Once created, the session will be in a "stopped" state. `c' may be used in place of `create'. start [options] SESSION [SESSION]... Start session(s). For each session specified, the session directory is registered in the runsvdir directory. The screen session will be attached to the serial terminal and logging of the terminal will begin. `s' may be used in place of `start'. options: -a (--all) to enable all sessions. restart [options] SESSION [SESSION]... Restart session(s). This sends running sessions a "restart" signal, and starts session that are not running. This can be used when changes have been made to the screenrc, for instance. `r' may be used in place of `restart'. options: -a (--all) to disable all sessions, -r (--running) to restart just the currently running sessions. stop [options] SESSION [SESSION]... Stop session(s). This kills the screen session attached to the serial terminal by sending it an "exit" signal, and then unregister- ing the session directory from the runsvdir directory. `k' may be used in place of `stop'. options: -a (--all) to disable all ses- sions. destroy [options] SESSION [SESSION]... Destroy session(s) entirely. This will destroy the session directory, including all history of the session and the logs. `d' may be used in place of `destroy'. options: -a (--all) to remove all sessions. list [SESSION]... List session(s). With no arguments, will list all sessions. The leading three characters in the list indicate: whether the session is running (+) or not (-) or in some unknown state (?), whether the user can attach to the session (a) or not (-), whether the user can follow the session (f) or not (-). If the session state is unknown (?), it's usually because the user asking for information about the session can't read the session stat file. `l' may be used in place of `list'. help Output a brief usage summary. `h' or `?' may be used in place of `help'. LOGS
Logs are handled by svlogd. For information on how to control session log handling, please see svlogd(8) and/or log-limits.txt from the documentation of this package. FILES
/etc/cereal/screenrc Default cereal screenrc file. /etc/cereal/cereal-admin.conf Configuration file to set parameters for session creation and management. /var/lib/cereal/sessions/$SESSION/screenrc Special screenrc file for session SESSION. The presence of this file overrides the default screenrc file /etc/cereal/screenrc. EXIT STATUS
Exit status is 0 if OK, 1 if minor problems, 2 if serious trouble. AUTHOR
Written by Jameson Rollins and Daniel Kahn Gillmor. BUGS
If the invoking user does not have read and execute access to the cereal session's supervise directory, `cereal-admin list' may not always indicate that session's status accurately. REPORTING BUGS
Report bugs to <cereal@fifthhorseman.net>. COPYRIGHT
Copyright (C) 2007 Jameson Rollins and Daniel Kahn Gillmor This is free software. You may redistribute copies of it under the terms of the GNU General Public License <http://www.gnu.org/licenses/gpl.html>. There is NO WARRANTY, to the extent permitted by law. SEE ALSO
cereal(1), screen(1), runsvdir(8), svlogd(8) cereal-admin 0.1 March 2007 CEREAL-ADMIN(8)
All times are GMT -4. The time now is 10:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy