public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andrew Tchernoivanov" <tchernoivanov@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] user command auditing
Date: Wed, 16 Jul 2008 23:11:35 +0400	[thread overview]
Message-ID: <dd58d2b90807161211lfcda457y9333aaf749bfa636@mail.gmail.com> (raw)
In-Reply-To: <20080716111351.S3305@shell.bway.net>

[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]

 >Is there a tool or a way of keeping track of which commands user's are
>executing on a system?

There is a .bash_history file in user's home folders. It contains all
commands executed by this user.

On Wed, Jul 16, 2008 at 7:22 PM, A. Khattri <ajai@bway.net> wrote:

> On Wed, 16 Jul 2008, Richard Marzan wrote:
>
>  I understand that history files can be wiped out
>> and they don't really contain the time at which a command and it's
>> arguments were run so I refrain from relying on it.
>>
>
> On traditional UNIX systems, system accounting logs (usually called acct)
> can be read via the lastcomm command. Im guessing that the sys-process/acct
> ebuild will give you those commands.
>
> NOTE: You will also need kernel support for process/login accounting - look
> for "process accounting" in your kernel config and make sure it is switched
> on. (Natrually, you will need to rebuild your kernel / modules if it isn't
> switched on and reboot to activate it).
>
>
> UPDATE: I just checked one of my kernels and the config option is called
> "BSD-style process accouting" - it lives in General Setup when configuring a
> kernel.
>
>
> --
> A
> --
> gentoo-user@lists.gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 1852 bytes --]

  reply	other threads:[~2008-07-16 19:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16  8:26 [gentoo-user] user command auditing Richard Marzan
2008-07-16 15:22 ` A. Khattri
2008-07-16 19:11   ` Andrew Tchernoivanov [this message]
2008-07-16 23:37     ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dd58d2b90807161211lfcda457y9333aaf749bfa636@mail.gmail.com \
    --to=tchernoivanov@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox