* Logging parameters
@ 2016-10-18 14:59 Nil .
2016-10-18 15:15 ` Steve Grubb
0 siblings, 1 reply; 2+ messages in thread
From: Nil . @ 2016-10-18 14:59 UTC (permalink / raw)
To: linux-audit
[-- Attachment #1.1: Type: text/plain, Size: 307 bytes --]
Hi, i would like to know if it is possible to log the parameters that a
command get's passed on,
i.e in the command ' ls -la', the logs only show comm="ls" and i would like
to have the full comm="ls -la".
is it possible anyhow using audit logs? do you know any other way to log
those parameters?
thank you
[-- Attachment #1.2: Type: text/html, Size: 427 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Logging parameters
2016-10-18 14:59 Logging parameters Nil .
@ 2016-10-18 15:15 ` Steve Grubb
0 siblings, 0 replies; 2+ messages in thread
From: Steve Grubb @ 2016-10-18 15:15 UTC (permalink / raw)
To: linux-audit
On Tuesday, October 18, 2016 4:59:58 PM EDT Nil . wrote:
> Hi, i would like to know if it is possible to log the parameters that a
> command get's passed on,
> i.e in the command ' ls -la', the logs only show comm="ls" and i would like
> to have the full comm="ls -la".
> is it possible anyhow using audit logs? do you know any other way to log
> those parameters?
These are captured in the PROCTITLE record of the event. If you do not have
that record attached to events, then you need a newer or patched kernel. So,
you should have it on a recent kernel.
-Steve
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-10-18 15:15 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-10-18 14:59 Logging parameters Nil .
2016-10-18 15:15 ` Steve Grubb
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox