From: Steve Dickson <SteveD@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Chuck Lever <chuck.lever@oracle.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] make capabilities support optional
Date: Mon, 26 Apr 2010 12:54:36 -0400 [thread overview]
Message-ID: <4BD5C54C.60705@RedHat.com> (raw)
In-Reply-To: <201004261251.12210.vapier@gentoo.org>
On 04/26/2010 12:51 PM, Mike Frysinger wrote:
> On Monday 26 April 2010 12:10:00 Steve Dickson wrote:
>> On 04/26/2010 11:24 AM, Chuck Lever wrote:
>>> At the very least, I think the man page should mention this bug somehow,
>>> and maybe a warning should be generated during the build. Since this is
>>> mostly for embedded systems, according to Mike, I doubt an actual
>>> generated run-time warning would be visible to anyone.
>>
>> Mike would you be willing to test this out and document any
>> differences in statd behaviour with and without that config
>> flag set?
>
> i think a BUGS section in statd is sufficient, but if you wanted to go
> further, then a simple syslog() would be OK as well. dumping warnings to
> stderr/stdout is obnoxious and non-standard for daemons. those really only
> should be written when a daemon is quitting due to misconfiguration.
I agree... a blurb in the BUGS section is all that is needed..
>
> i can send a patch for the man page, but i'd only copy and paste what Chuck
> wrote (about statd remaining registered upon exit).
That would be good... thanks!
steved.
prev parent reply other threads:[~2010-04-26 16:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 8:46 [PATCH] make capabilities support optional Mike Frysinger
2010-04-23 16:29 ` Steve Dickson
[not found] ` <4BD1CADD.4050200-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-04-23 17:28 ` Chuck Lever
2010-04-23 18:22 ` Steve Dickson
[not found] ` <4BD1E55B.2090703-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-04-23 19:12 ` Chuck Lever
2010-04-23 19:29 ` Mike Frysinger
2010-04-23 20:09 ` Chuck Lever
2010-04-24 4:42 ` Mike Frysinger
2010-04-26 15:12 ` Chuck Lever
2010-04-26 16:46 ` Mike Frysinger
2010-04-26 18:03 ` Chuck Lever
2010-04-23 22:22 ` Steve Dickson
[not found] ` <4BD21DA1.4000001-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-04-26 15:24 ` Chuck Lever
2010-04-26 16:10 ` Steve Dickson
[not found] ` <4BD5BAD8.5040209-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-04-26 16:51 ` Mike Frysinger
2010-04-26 16:54 ` Steve Dickson [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=4BD5C54C.60705@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=vapier@gentoo.org \
/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;
as well as URLs for NNTP newsgroup(s).