If your shell honors $HISTFILE you can create a history file anywhere you want during login
We have ours like this
Code:
/home/[somewhere]/.ihist/.sh_hist_jmcnama
All of the interactive users' histories are there in the same .ihist directory. We set HISTSIZE=1000 to keep track for a while. This allows an easy scan of history to find out "whodunit" if there is a security problem.
This is a SOX requirement - be able to look up all interactives users commands for the past 30 days. We have accounting turned on too.
Hi All,
Whenever I log in to my terminal and execute some cmds and then I type "history", I get the list of all the commands that I have executed.
I want to know where is the history been stored (any path location ?)
Secondly,if I want to delete the history or some part of the history, can... (9 Replies)
How do I pipe serveral commans that will list only the user ids, sort the output, and remove any duplice name entries for those that have logged in in the past month? Thanks! (1 Reply)
Hi,
I need to access a user's command history. However, the dilemma is that he is logged in and so his current history is not yet flushed to .bash_history file which gets flushed when he logs out. Is there a way I can still access his most recent history?
thank you,
S (4 Replies)
Under oracle user file abc.txt was created. Oracle user belong to dba group on UNIX Server. However other non Oracle users which belongs to some other network groups need read only access to this file.
Every time when I login as other then oracle user and try to view this file it saying that I... (2 Replies)
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)
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)
Hello,
I have a a directory dir1 with permissions 700 (yes wantedly) and is owned by user1:group1
rwx------ user1 group1 dir1I need to give permissions to user2 (belongs to group2) on dir1 and its files, so I granted the permissions using setfacl ; instead of adding the user to groups and... (3 Replies)
Discussion started by: karumudi7
3 Replies
LEARN ABOUT HPUX
acctdusg
acct(1M)acct(1M)NAME
acct: acctdisk, acctdusg, accton, acctwtmp, closewtmp, utmp2wtmp - overview of accounting and miscellaneous accounting commands
SYNOPSIS
file] file]
[file]
reason
DESCRIPTION
Accounting software is structured as a set of tools (consisting of both C programs and shell procedures) that can be used to build account-
ing systems. The shell procedures, described in acctsh(1M), are built on top of the C programs.
Connect time accounting is handled by various programs that write records into the The programs described in acctcon(1M) convert this file
into session and charging records which are then summarized by (see acctmerg(1M)).
Process accounting is performed by the HP-UX system kernel. Upon termination of a process, one record per process is written to a file
(normally The programs in acctprc(1M) summarize this data for charging purposes; is used to summarize command usage (see acctcms(1M)).
Current process data can be examined using (see acctcom(1M)).
Process accounting and connect time accounting (or any accounting records in the format described in acct(4)) can be merged and summarized
into total accounting records by (see the format in acct(4)). is used to format any or all accounting records (see acctsh(1M)).
reads lines that contain user ID, login name, and number of disk blocks, and converts them to total accounting records that can be merged
with other accounting records.
reads its standard input (usually from and computes disk resource consumption (including indirect blocks) by login. Only files found under
login directories (as determined from the password file) are accounted for. All files under a login directory are assumed to belong to
that user regardless of actual owner. If is given, records consisting of those file names for which charges no one are placed in file (a
potential source for finding users trying to avoid disk charges). If is given, file is the name of the password file. This option is not
needed if the password file is (See diskusg(1M) for more details.)
turns process accounting off if the optional file argument is omitted. If file is given, it must be the name of an existing file, to which
the kernel appends process accounting records (see acct(2) and acct(4)).
writes a utmp record to its standard output if the option is not used. If the option is used, writes a record to The record contains the
current time and a string of characters that describe the reason for writing the record. A record type of is assigned (see utmp(4) and
utmps(4)). The string argument reason must be 11 or fewer characters, numbers, or spaces if option is not used. Otherwise, it must be 63
or fewer characters, numbers, or spaces. For example, the following are suggestions for use in reboot and shutdown procedures, respec-
tively:
writes a record, for each user currently logged in, to the file This program is invoked by runacct to close the existing file before creat-
ing a new one.
writes a record, for each user currently logged in, to the file This program is invoked by runacct to initialize the newly created file.
FILES
Holds all accounting commands listed in section(1M) of this manual.
Current process accounting file.
Used for converting login name to user ID
Login/logoff history file.
New login/logoff history database.
SEE ALSO acctcms(1M), acctcom(1M), acctcon(1M), acctmerg(1M), acctprc(1M), acctsh(1M), diskusg(1M), fwtmp(1M), runacct(1M), acct(2), acct(4),
utmp(4). utmps(4), wtmps(4).
STANDARDS CONFORMANCE acct(1M)