From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Abhishek Gupta <abhikiki@gmail.com>
Subject: Re: some problem with my event dispatcher
Date: Mon, 17 Dec 2007 08:46:57 -0500 [thread overview]
Message-ID: <200712170846.57826.sgrubb@redhat.com> (raw)
In-Reply-To: <18436f8f0712170010k59a65102kaf1cffb7c4566d35@mail.gmail.com>
On Monday 17 December 2007 03:10:46 Abhishek Gupta wrote:
> + fp=fopen("tempfile.txt","w+");
> + fwrite((char*)data,sizeof(char),30,fp);
> + fclose(fp);
What directory is your dispatcher using for cwd? Try giving a full path to a
directory it is allowed to write in. There are no restrictions on where the
dispatcher can write unless selinux policy prevents it. That is easily
checked by trying "setenforce 0".
-Steve
prev parent reply other threads:[~2007-12-17 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 8:10 some problem with my event dispatcher Abhishek Gupta
2007-12-17 13:46 ` Steve Grubb [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=200712170846.57826.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=abhikiki@gmail.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