11-06-2001
Certainly points to the accounting solution once again, espcially if you have a savy user who knows he is being monitored in this way. Of course, the user would need to suspect that he was being monitored in this way, but sometimes what seems unlikely happens and I can see this taking place.
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
RPC.STATD(8) BSD System Manager's Manual RPC.STATD(8)
NAME
rpc.statd -- host status monitoring daemon
SYNOPSIS
rpc.statd [-d]
DESCRIPTION
rpc.statd is a daemon which co-operates with rpc.statd daemons on other hosts to provide a status monitoring service. The daemon accepts
requests from programs running on the local host (typically, rpc.lockd(8), the NFS file locking daemon) to monitor the status of specified
hosts. If a monitored host crashes and restarts, the remote daemon will notify the local daemon, which in turn will notify the local pro-
gram(s) which requested the monitoring service. Conversely, if this host crashes and restarts, when rpc.statd restarts, it will notify all
of the hosts which were being monitored at the time of the crash.
Options and operands available for rpc.statd :
-d The -d option causes debugging information to be written to syslog, recording all RPC transactions to the daemon. These messages are
logged with level LOG_DEBUG and facility LOG_DAEMON. Error conditions are logged irrespective of this option, using level LOG_ERR.
The rpc.statd daemon must NOT be invoked by inetd(8) because the protocol assumes that the daemon will run from system start time. Instead,
it should be configured in rc.conf(5) to run at system startup.
FILES
/var/db/statd.status non-volatile record of currently monitored hosts.
/usr/include/rpcsvc/sm_inter.x RPC protocol specification used by local applications to register monitoring requests.
SEE ALSO
syslog(3), rc.conf(5), rpc.lockd(8)
STANDARDS
The implementation is based on the specification in X/Open CAE Specification C218, "Protocols for X/Open PC Interworking: XNFS, Issue 4",
ISBN 1 872630 66 9
HISTORY
A version of rpc.statd appeared in SunOS 4.
BUGS
There is no means for the daemon to tell when a monitored host has disappeared permanently (e.g., catastrophic hardware failure), as opposed
to transient failure of the host or an intermediate router. At present, it will retry notification attempts at frequent intervals for 10
minutes, then hourly, and finally gives up after 24 hours.
The protocol requires that symmetric monitor requests are made to both the local and remote daemon in order to establish a monitored rela-
tionship. This is convenient for the NFS locking protocol, but probably reduces the usefulness of the monitoring system for other applica-
tions.
The current implementation uses more than 1Kbyte per monitored host in the status file (and also in VM). This may be inefficient for NFS
servers with large numbers of clients.
BSD
September 19, 1995 BSD