11-06-2001
Well, what if the user did this:
mv .bash_history .junk; ln -s /dev/null .bash_history
If the directory was writable, you may be able to do this even if the file wouldn't normally able to do this...
Also, if the user made that a hard link, the cronjob would always copy a null file...
Also, bash will usually not write out the history until the log out of the shell...
accounting is the best thing I can think of...
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
we need the help to change .bash_histroy file in root ,(i.e) we want to save the histroy for .temp.txt for permenently. how to do??
Help us (1 Reply)
Discussion started by: thakshina
1 Replies
2. UNIX for Advanced & Expert Users
During the course of the session before I logout I see some of the commands listed from my previous session but not from my current session and after I logout and log back in I see the commands which I ran before logging out.
Does the .bash_history stay in the buffer or someplace else then?
... (2 Replies)
Discussion started by: jacki
2 Replies
3. Shell Programming and Scripting
Dear All,
I am creating users on our servers. the .bash_history supposed to store all the commands entered by the user. My question is, how can I prevent the user himself from editing or viewing this file?
I have tried chaning the owner of the .bash_history to be the root user but... (5 Replies)
Discussion started by: charbel.n.s
5 Replies
4. UNIX for Advanced & Expert Users
Hi Experts,
I know my question would be strange but i need to understand how the .bash_history file is logging user actions (the mechanism) and if possible modify it to include also the date/time of every action done by the user.
Sample file:
# more .bash_history
ssh <IP address> -l axadmin... (3 Replies)
Discussion started by: Dendany83
3 Replies
5. UNIX for Dummies Questions & Answers
Hi - user commands are written in . bash_history of that user when he logs out. my bash_history file shows. not sure what that number means
#1329618972
ls -la
#1329618978
ls
#1329618980
ls -la
my bash_profile looks like this
PATH=$PATH:$HOME/bin
export PATH
export... (3 Replies)
Discussion started by: oraclermanpt
3 Replies
6. UNIX for Advanced & Expert Users
rm -rf .bash_history some one ran rm -rf .bash_history on my Linux server(SUSE),I can see this command being run in current history, but I want the OLD history as well,can I recover the old history back. (9 Replies)
Discussion started by: Ankit Bansal
9 Replies
7. Shell Programming and Scripting
Hi would like to ask if there is anyway to display .bash_history with timestamp using shell script?
i know that you should use history command with HISTTIMEFORMAT="%d/%m/%y %T " to display it in terminal but it does not work when i use it on shell script. It seem that you can't run history... (1 Reply)
Discussion started by: pikamon
1 Replies
8. UNIX for Beginners Questions & Answers
I am using the bash shell.
When I view my recent command history using the "history" command from the prompt, it only shows me the commands starting at #928.
The commands I need are earlier than that, but I can't figure out how to make the other 927 display.
They are in my .bash_history... (1 Reply)
Discussion started by: Twinklefingers
1 Replies
null(n) null(n)
__________________________________________________________________________________________________________________________________________________
NAME
null - Create and manipulate null channels
SYNOPSIS
package require Tcl
package require memchan
null
_________________________________________________________________
DESCRIPTION
The command described here is only available in a not-yet released version of the package. Use the CVS to get the sources.
null creates a null channel which absorbs everything written into it. Reading from it is not possible, or rather will always return zero
bytes. These channels are essentially Tcl-specific variants of the null device for unixoid operating systems (/dev/null). Transfer-
ing the generated channel between interpreters is possible but does not make much sense.
OPTIONS
Memory channels created by null provide one additional option to set or query.
-delay ?milliseconds?
A null channel is always writable and readable. This means that all fileevent-handlers will fire continuously. To avoid starvation
of other event sources the events raised by this channel type have a configurable delay. This option is set in milliseconds and
defaults to 5.
A null channel is always writable and never readable. This means that a writable fileevent-handler will fire continuously and a readable
fileevent-handler never at all. The exception to the latter is only the destruction of the channel which will cause the delivery of an eof
event to a readable handler.
SEE ALSO
fifo, fifo2, memchan, random, zero
KEYWORDS
channel, i/o, in-memory channel, null
COPYRIGHT
Copyright (c) 1996-2003 Andreas Kupries <andreas_kupries@users.sourceforge.net>
Memory channels 2.2 null(n)