From: geckiv <geckiv@optonline.net>
To: linux-audit@redhat.com
Subject: Re: Writting to audit with an application
Date: Sun, 18 Mar 2007 17:15:13 -0400 [thread overview]
Message-ID: <45FDABE1.4010609@optonline.net> (raw)
In-Reply-To: <200703171850.59897.sgrubb@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 482 bytes --]
Steve,
I updated my kernel and that seemed to fix the problem.
Thanks,
Frank
Steve Grubb wrote:
>On Saturday 17 March 2007 17:34:57 geckiv wrote:
>
>
>>FAILURE: errno = 22
>>Error writing audit file: Invalid argument
>>
>>
>
>I bet this is the problem. ^^^^ EINVAL. That can be bad arguments or
>sometimes a permission problem from selinux.
>
>
>
>>Error writing audit: Illegal seek
>>
>>
>
>This was probably a changed errno from perror.
>
>-Steve
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 1048 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2007-03-18 21:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-17 18:54 Writtign to audit with an application geckiv
2007-03-17 20:59 ` Steve Grubb
2007-03-17 21:34 ` Writting " geckiv
2007-03-17 22:24 ` Steve Grubb
2007-03-19 19:58 ` geckiv
2007-03-19 21:38 ` Steve Grubb
2007-03-17 22:50 ` Steve Grubb
2007-03-18 21:15 ` geckiv [this message]
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=45FDABE1.4010609@optonline.net \
--to=geckiv@optonline.net \
--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