From: salgak@comcast.net
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: Audit: audisp-remote plugin: why is OpenLDAP a dependency ??
Date: Mon, 9 Feb 2015 17:26:15 +0000 (UTC) [thread overview]
Message-ID: <1286467080.2438459.1423502775408.JavaMail.zimbra@comcast.net> (raw)
In-Reply-To: <20150209180058.54f930bd@ivy-bridge>
[-- Attachment #1.1: Type: text/plain, Size: 950 bytes --]
Yeah, just crawled into the rpm and saw that. Going to try to re-spin a smaller RPM without the zos and see if that works.
----- Original Message -----
From: "Steve Grubb" <sgrubb@redhat.com>
To: salgak@comcast.net
Cc: linux-audit@redhat.com
Sent: Monday, February 9, 2015 12:00:58 PM
Subject: Re: Audit: audisp-remote plugin: why is OpenLDAP a dependency ??
On Mon, 9 Feb 2015 13:47:36 +0000 (UTC)
salgak@comcast.net wrote:
> I'm currently dealing with a VMware appliance, and need to export my
> audit logs. Despite VMware telling me to use the audisp-remote plugin
> with auditd, I get a dependency check for OpenLDAP, and the install
> fails.
>
> I'm pointing to my audit server (a Splunk box) via IP address. Is
> there any workaround, or am I stuck adding even MORE software to the
> appliance ??
The package the plugin is included in contains all of them. The
zos-remote plugin is the one that wants openldap.
-Steve
[-- Attachment #1.2: Type: text/html, Size: 1561 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-02-09 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <924112195.2223087.1423489490422.JavaMail.zimbra@comcast.net>
2015-02-09 13:47 ` Audit: audisp-remote plugin: why is OpenLDAP a dependency ?? salgak
2015-02-09 17:00 ` Steve Grubb
2015-02-09 17:26 ` salgak [this message]
2015-02-10 19:01 ` salgak
2015-02-12 19:42 ` Steve Grubb
2015-02-12 22:22 ` Keith A. Glass
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=1286467080.2438459.1423502775408.JavaMail.zimbra@comcast.net \
--to=salgak@comcast.net \
--cc=linux-audit@redhat.com \
--cc=sgrubb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.