06-10-2009
As far as I know there is no way of preventing a user from deleting their history in bash.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello All,
I have a new HPUX system going into production and it will be used by 2 projects. One of the contract requirements is the 2 groups can not have access to the others work or data. I believe I have the system pretty well locked up using groups and permissions and selective mounting of... (2 Replies)
Discussion started by: DanL
2 Replies
2. UNIX for Advanced & Expert Users
We have a shared development box, running Solaris 10 that is an NIS client, all the developers have local root password. If they know the NIS uid of another user, they can just do
% useradd -u <uid> login
And then log in as that user and have full access to his files in his home directory. ... (3 Replies)
Discussion started by: nfw
3 Replies
3. UNIX for Dummies Questions & Answers
I have just set up a user on our system HP-Thru64. The user needs to be able to su to root after they login and this works fine. Users cannot login from root externally so you have to first connect as a user and then su. I am wondering is it possible for me to prevent the user from having telnet... (4 Replies)
Discussion started by: peragin
4 Replies
4. IP Networking
hi all,
i want to prevent users downloading files in the office as bandwidth becomes very low
and affects work.
one of my friend tried to close the connection using ethercap but this does not work.
i have a debian desktop while other users use MS W!ndows.
Please provide any help. Thanks (5 Replies)
Discussion started by: coolatt
5 Replies
5. UNIX Desktop Questions & Answers
Hi All,
I have the below code where Iam connecting from xzur111pap server to xzur0211pap server thru ssh to execute some commands.
ssh xzur0211pap
spaceleft=`df -k /home |tail -1 | awk '{print $5}'`
spaceleft=${spaceleft%\%}
if ]; then
echo "ALERT : HUFS(/home $spaceleft)"
exit 0... (3 Replies)
Discussion started by: gaddamja
3 Replies
6. Shell Programming and Scripting
Good Evening all,
After spending the last week or so reading many posts I decided to register and join in. This is my first post on the forum so please forgive me as im new to this, Im after some help in throwing together a quick basic script without using expect to change the password on several... (4 Replies)
Discussion started by: mutley2202
4 Replies
7. Shell Programming and Scripting
Hi could some let me know how to prevent user from changing his home directory.......
Thanks in advance.... (1 Reply)
Discussion started by: Revanth547
1 Replies
8. Shell Programming and Scripting
Hi could some let me know how to prevent user from changing his home directory.......
Thanks in advance.... (6 Replies)
Discussion started by: rahul547
6 Replies
9. AIX
Hi Folks,
Any system admin did provide AIX file system control to prevent user/ admin accidentally remove database files ?
Thanks. (4 Replies)
Discussion started by: ckwan
4 Replies
10. UNIX for Advanced & Expert Users
Hi Experts,
Need your support
Redhat 6.5
I want to create a user with all(read, write, execute) privileges except that user should not be able to create any new user from his login
to perform any task. (10 Replies)
Discussion started by: as7951
10 Replies
LEARN ABOUT MOJAVE
tklib_history
history(n) Provides a history for Entry widgets history(n)
__________________________________________________________________________________________________________________________________________________
NAME
history - Provides a history for Entry widgets
SYNOPSIS
package require Tcl 8.4
package require Tk 8.4
package require history ?0.1?
::history::init pathName ?length?
::history::remove pathName
::history::add pathName text
::history::get pathName
::history::clear pathName
::history::configure pathName option ?value?
bell
_________________________________________________________________
DESCRIPTION
This package provides a convenient history mechanism for Entry widgets. The history may be accessed with the up and down arrow keys.
::history::init pathName ?length?
Arranges to remember the history of the named Entry widget. An optional length determines the number of history entries to keep.
This may be changed later with ::history::configure. History entries must be added with the ::history::add command before they can
be seen.
::history::remove pathName
Forgets all history entries for the Entry pathName and removes the history bindings.
::history::add pathName text
This command is used to add history entries to an Entry that has previously had ::history::init called on it. This command should be
called from your Entry handler with the contents of the entry (or whatever you wish to add to the history).
::history::get pathName
This command returns a list containing the history entries for the Entry pathName
::history::clear pathName
This command clears the history list for the named Entry.
::history::configure pathName option ?value?
This command queries or sets configuration options. Currently the options recognized are length and alert. Setting the length deter-
mines the number of history entries to keep for the named Entry. Alert specifies the command to run when the user reaches the end of
the history, it defaults to
bell
entry .e
bind .e <Return> [list ProcessEntry %W]
::history::init .e
pack .e
proc ProcessEntry {w} {
set text [$w get]
if {$text == ""} { return }
::history::add $w $text
puts $text
$w delete 0 end
}
KEYWORDS
entry, history
history 0.1 history(n)