From: Chris Wright <chrisw@osdl.org>
To: Steve G <linux_4ever@yahoo.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, selinux@tycho.nsa.gov
Subject: Re: Signal problem
Date: Tue, 26 Apr 2005 13:28:00 -0700 [thread overview]
Message-ID: <20050426202759.GD493@shell0.pdx.osdl.net> (raw)
In-Reply-To: <20050426201806.58515.qmail@web51501.mail.yahoo.com>
* Steve G (linux_4ever@yahoo.com) wrote:
> >Isn't this unreliable anyway, e.g. your hook might queue up the audit
> >message for processing by auditd, but auditd gets the signal before it
> >handles the message and exits without emptying the queue?
>
> The message would be in syslog in that scenario. It isn't there either.
Upon termination, what's queued to the netlink socket but not yet
received is going to be lost, right? Perhaps you need to be able to set
pid == 0, and still drain the fd when you recieve a TERM?
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2005-04-26 20:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 20:18 Signal problem Steve G
2005-04-26 20:28 ` Chris Wright [this message]
2005-04-27 11:25 ` Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2005-04-26 20:38 Steve G
2005-04-26 20:48 ` Chris Wright
2005-04-26 19:23 Steve G
2005-04-26 19:51 ` Stephen Smalley
2005-04-26 20:13 ` Chris Wright
2005-04-26 19:56 ` Stephen Smalley
2005-04-26 20:16 ` Chris Wright
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=20050426202759.GD493@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux_4ever@yahoo.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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.