From: Miloslav Trmac <mitr@redhat.com>
To: Dan Gruhn <Dan.Gruhn@GroupW.com>
Cc: linux-audit@redhat.com
Subject: Re: audit-viewer
Date: Mon, 2 Mar 2009 16:07:29 -0500 (EST) [thread overview]
Message-ID: <491158387.202811236028049655.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <49AC48CE.8050706@GroupW.com>
Hello,
----- "Dan Gruhn" <Dan.Gruhn@GroupW.com> wrote:
> You are right, the path was /usr/local/var/log/audit. Once I recompiled
> with this change everything seems to be working. Does this default of
> --prefix subree make sense in any situation? I ask because perhaps a
> default of /var would more often produce the correct result.
I personally use a different prefix for development and installation without root privileges - but I could of course use an extra option for that.
In general, I don't think overriding localstatedir in audit-viewer is worth it. It violates user's expectations about ./configure behavior, and autoconf doesn't offer a clean way to override it anyway. After all, most users should (eventually) rely on their distribution to package audit-viewer for them.
Mirek
next prev parent reply other threads:[~2009-03-02 21:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1241228806.180461236014459986.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2009-03-02 17:22 ` audit-viewer Miloslav Trmac
2009-03-02 20:59 ` audit-viewer Dan Gruhn
2009-03-02 21:07 ` Miloslav Trmac [this message]
[not found] <1162925222.89101235079087226.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2009-02-19 21:31 ` audit-viewer Miloslav Trmac
2009-02-20 17:36 ` audit-viewer Dan Gruhn
2009-02-20 20:32 ` audit-viewer Miloslav Trmac
2009-03-02 16:38 ` audit-viewer Dan Gruhn
2009-02-19 21:09 audit-viewer Dan Gruhn
2009-02-19 21:20 ` audit-viewer Steve Grubb
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=491158387.202811236028049655.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com \
--to=mitr@redhat.com \
--cc=Dan.Gruhn@GroupW.com \
--cc=linux-audit@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