From: LC Bruzenak <lenny@magitekltd.com>
To: Miloslav Trmac <mitr@redhat.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: print capability for audit-viewer?
Date: Sat, 19 Dec 2009 11:58:12 -0600 [thread overview]
Message-ID: <cecd18b00912190958y6b56711fg78f74e3e9e4ab8a7@mail.gmail.com> (raw)
In-Reply-To: <1500542438.174911261206227331.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
On Sat, Dec 19, 2009 at 1:03 AM, Miloslav Trmac <mitr@redhat.com> wrote:
> ----- "LC Bruzenak" <lenny@magitekltd.com> wrote:
>> Is there any plan to add printing capability to the audit-viewer?
> Not currently; you can export any tab to HTML[1] and use a web browser (or perhaps (lynx -dump | lpr)) to print it. Is that an acceptable solution for you?
> Mirek
Mirek,
Thanks for the reply. I tried the export, however it isn't the tab
contents per se which have the important data for us. We have modified
the event tab to include the entire raw event, because in our system,
the really important data is in usually the application-submitted
text.
Since the event details window has no export, there is no way to print
the desired information per event.
I also tried adding the "other fields" to the columns listing, however
that particular test also had a different error. The first column was
"Date" and when I tried to export that list, it failed to export the
list. So I ran the audit-viewer from the command line and saw an
error:
TypeError: __date_column_event_text takes exactly 1 argument (2 given).
>
> [1] I have just noticed that "list" exports don't work, and a fix will be available in the next release.
> Mirek
>
Was it the above or different?
Thanks again,
LCB.
--
LC (Lenny) Bruzenak
next prev parent reply other threads:[~2009-12-19 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <425706905.174891261206096006.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2009-12-19 7:03 ` print capability for audit-viewer? Miloslav Trmac
2009-12-19 17:58 ` LC Bruzenak [this message]
2009-12-21 13:12 ` Miloslav Trmac
2009-12-17 21:57 LC Bruzenak
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=cecd18b00912190958y6b56711fg78f74e3e9e4ab8a7@mail.gmail.com \
--to=lenny@magitekltd.com \
--cc=linux-audit@redhat.com \
--cc=mitr@redhat.com \
/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