Sponsored Content
Top Forums Shell Programming and Scripting How to kill history from terminal to others using same id Post 302167490 by sb008 on Thursday 14th of February 2008 02:44:14 PM
Old 02-14-2008
Quote:
Originally Posted by dsravan
I cant edit the .profile as every body uses this bacuase of the same id we all use. The reason I want this is there are people in the team who constantly try to see what others are doing. I am seeing for something i can do from my terminal with out editing any profiles to kill histiry coming out from my terminal? is it possible?
If you edit the .profile as I mentioned, everybody will maintain the same functionality, each session will only use a different history file.

another option would be to enter on your command line:

HISTSIZE=0
export HISTSIZE

However, then you completely loose the history functionality
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Add pseudo terminal to bash history

Hello, Could you tell me if it is possible to add pseudo terminal name to the bash history? I need to see from which terminal the command was issues. I found a variable HISTTIMEFORMAT that helps me to identify the time but cannot find similar thing for the pts number. thanks, Pavel. (0 Replies)
Discussion started by: pn8830
0 Replies

2. Shell Programming and Scripting

How to clear history logs of all terminal sessions

Hi, I would normally clear off the history entries from a terminal by using the following commands: > ~/.bash_history history -c But this will remove the entries of that particular session only. How to prune all the entries of all login sessions for a particular user in a system? N.B:... (3 Replies)
Discussion started by: royalibrahim
3 Replies

3. Shell Programming and Scripting

Funny : why can't I kill my parent terminal in a script ?

Hellooooooo ;) Today I've created a script that does some things (not important). And for fun I want that it kills the terminal from which I launch it. (too lazy to press Alt-F4 lol) So I write #!/bin/bash kill $PPID but it doesn't work ... while if in my xterm I launch another xterm... (8 Replies)
Discussion started by: xib.be
8 Replies

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

5. Shell Programming and Scripting

Replicate history commands in multiple terminal

Hi, I am using putty client to connect to my remote Linux server box, and I am connecting through ssh. That system runs bash shell. So, if I use multiple putty terminal, how can I replicate those commands that I ran in other terminals to be available/shared in the current terminal window (i.e)... (1 Reply)
Discussion started by: royalibrahim
1 Replies

6. Shell Programming and Scripting

shell script to kill process with respect to terminal

Hi, I've a script which kills all process, but i need a script shell script(sh), where it'll kill process on that particular terminal. below is example TY=`tty` for P in $TY do `kill -9 $P 2>/dev/null`; done echo "test process killed" break ... (3 Replies)
Discussion started by: asak
3 Replies

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

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

9. Shell Programming and Scripting

Kill an specific process ID using the KILL and GREP commands

Good afternoon I need to KILL a process in a single command sentence, for example: kill -9 `ps -aef | grep 'CAL255.4ge' | grep -v grep | awk '{print $2}'` That sentence Kills the process ID corresponding to the program CAL255.4ge. However it is possible that the same program... (6 Replies)
Discussion started by: enriquegm82
6 Replies

10. Shell Programming and Scripting

Kill specific terminal using shell/bash

Hello elite shell/bash specialists, I have done plenty of STFW and some RTFM, but I cannot find a clear solution to my challenge Goal: My goal is to have a script(of any language, preferably shell/bash/anything that can run things on unix), which will kill specific unix terminal windows for... (0 Replies)
Discussion started by: kamil-mech
0 Replies
LEDIT(1)						      General Commands Manual							  LEDIT(1)

NAME
ledit - line editor, version 2.03 SYNOPSIS
ledit [-h file] [-x] [-t] [-l length] [-a | -u] [command options] DESCRIPTION
The command ledit allows to edit lines one by one when running an interactive command. When typing a line, some keys with control or meta are interpreted: it is possible to insert characters in the middle of the line, go to the beginning or the end of the line, get a previous line, search for a line with a pattern, etc. OPTIONS
The options are: -h file Save the lines typed (history) in file. The default is to have them only in memory (so, they are lost at the end of the program). -x Extend the history file (given in option "-h") if it already exists. The default is to truncate the history file. -t Display the sequences generated by the keys (for debugging). -v Print ledit version and exit. -l length Tells that length is the maximum line length displayed. If the line edited is longer than this length, the line scrolls horizon- tally, while editing. The default value is 70. -a Ascii encoding: characters whose code is greater than 128 are displayed with a backslash followed by their code. -u Unicode encoding: the terminal must have been set in unicode mode. See commands unicode_start and unicode_stop. command options Runs the command command and its possible options. This must be the last option of ledit. The default value is "cat". KEYS BINDINGS
When ledit starts, some default key bindings are defined. The can be completed with a "leditrc" file. See the section LEDITRC. In the following lines, the caret sign "^" means "control" and the sequence "M-" means "meta" (either with the "meta" prefix, or by press- ing the "escape" key before). Examples: ^a press the "control" key, then press "a", then release "a", then release "control". M-a press the "meta" key, then press "a", then release "a", then release "meta", or: press and release the "escape" key, then press and release "a" (the manipulation with "meta" may not work in some systems: in this case, use the manipulation with "escape"). The default editing commands are: ^a : beginning of line ^e : end of line ^f : forward char ^b : backward char M-f : forward word M-b : backard word TAB : complete file name ^p : previous line in history ^n : next line in history M-< : first line in history M-> : last line in history ^r : reverse search in history (see below) ^d : delete char (or EOF if the line is empty) ^h : (or backspace) backward delete char ^t : transpose chars M-c : capitalize word M-u : upcase word M-l : downcase word M-d : kill word M-^h : (or M-del or M-backspace) backward kill word ^q : insert next char M-/ : expand abbreviation ^k : cut until end of line ^y : paste ^u : line discard ^l : redraw current line ^g : abort prefix ^c : interrupt ^z : suspend ^ : quit return : send line ^x : send line and show next history line other : insert char The arrow keys can be used, providing your keyword returns standard key sequences: up arrow : previous line in history down arrow : next line in history right arrow : forward char left arrow : backward char Other keys: home : beginning of line end : end of line delete : delete char page up : previous line in history page down : next line in history shift home : beginning of history shift end : end of history REVERSE SEARCH
The reverse search in incremental, i.e. ledit backward searchs in the history a line holding the characters typed. If you type "a", its search the first line before the current line holding an "a" and displays it. If you then type a "b", its search a line holding "ab", and so on. If you type ^h (or backspace), it returns to the previous line found. To cancel the search, type ^g. To find another line before holding the same string, type ^r. To stop the editing and display the current line found, type "escape" (other commands of the normal editing, different from ^h, ^g, and ^r stop the editing too). Summary of reverse search commands: ^g : abort search ^r : search previous same pattern ^h : (or backspace) search without the last char del : search without the last char any other command : stop search and show the line found LEDITRC
If the environment variable LEDITRC is set, it contains the name of the leditrc file. Otherwise it is the file named ".leditrc" in user's home directory. When starting, ledit reads this file, if it exists, to modify or complete the default bindings. If this file is changed while reading lines, it is read again to take the new file into account. Bindings lines are the ones which start with a string defining the key sequence and follow with a colon and a binding. A binding is either a string or a command. The other lines are ignored For example,the line: "C-a": beginning-of-line binds the sequence "control-a" to the command "beginning-of-line". The key sequence may contain the specific meta-sequences: C- followed by a key: "control" of this key M- followed by a key: "meta" of this key e the "escape" key nn where nnn is one, two, or three octal digits, or: xnn where nn is one or two hexadecimal digits: the binary representation of a byte a bell = C-g  backspace = C-h d delete = 277 f form feed = C-l newline = C-j carriage return = C-m tabulation = C-i v vertical tabulation = C-k The commands are: abort: do nothing accept-line: send the current line backward-char: move the cursor to the previous character backward-delete-char: delete the previous character backward-kill-word: delete the previous word backward-word: move the cursor before the previous word beginning-of-history: display the first line of the history beginning-of-line: move the cursor at the beginning of the line capitalize-word: uppercase the first char and lowercase the rest delete-char: delete the character under the cursor delete-char-or-end-of-file: same but eof if no character in the line downcase-word: lowercase whole word end-of-history: display the last line of the history end-of-line: move the cursor to the end of the line expand-abbrev: try to complete the word by looking at the history expand-to-file-name: try to complete the word from a file name forward-char: move the cursor after the next word forward-word: move the cursor to the next character interrupt: interrupt command (send control-C) kill-line: delete from the cursor to the end and save in buffer kill-word: delete the next word next-history: display the next line of the history operate-and-get-next: send line and display the next history line previous-history: display the previous line of the history quit: quit ledit quoted-insert: insert the next character as it is redraw-current-line: redisplay the current line reverse-search-history: backward search in the history suspend: suspend ledit (send control-Z) transpose-chars: exchange the last two characters unix-line-discard: kill current line upcase-word: uppercase whole word yank: insert kill buffer KNOWN BUGS
If ledit has been launched in a shell script, the suspend command kills it and its command... Use "exec ledit comm" instead of "ledit comm". The suspend command stops ledit but not the called program. Do not do this if the called program is not waiting on standard input. In some systems (e.g. alpha), pasting two many characters works bad and may block the terminal. Probably a kernel problem. No solution. SEE ALSO
unicode_start(1), unicode_stop(1). AUTHOR
Daniel de Rauglaudre, at INRIA, france. daniel.de_rauglaudre@inria.fr INRIA
Wed Jan 23, 2008 LEDIT(1)
All times are GMT -4. The time now is 01:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy