Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Olaf Kirch <okir@suse.de>, Neil Brown <neilb@suse.de>,
	Steve Dickson <SteveD@redhat.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: nfs-utils: support/nfs/rpcmisc.c
Date: Wed, 28 Jan 2009 13:17:07 -0500	[thread overview]
Message-ID: <20090128131707.401de2f1@tleilax.poochiereds.net> (raw)
In-Reply-To: <2B35C807-B7FD-4E6E-9660-0F3268CB890A@oracle.com>

On Wed, 28 Jan 2009 13:05:39 -0500
Chuck Lever <chuck.lever@oracle.com> wrote:

> On Jan 28, 2009, at 11:37 AM, Jeff Layton wrote:
> > On Tue, 27 Jan 2009 15:20:02 -0500
> > Chuck Lever <chuck.lever@oracle.com> wrote:
> >> I'm considering creating a version of rpc_init() under utils/statd
> >> that strips out all of the unnecessary features, uses note() instead
> >> of xlot(), and then adds support for AF_INET6.
> >>
> >
> > Is there some reason to not just convert statd to use xlog()? It
> > seems like that would be a better long term solution.
> 
> I'm not sure what the advantage of note() vs. xlog() is.
> 
> Be it also noted that sm-notify uses yet another logging mechanism,  
> and I've already coded up patches to move it over to using note().   
> This is because I'm adding some IPv6-enabled RPC handlers that are  
> shared with statd...
> 
> And, the RPC libraries also write directly to stderr.  All of those  
> error messages are lost in the daemon case, but when using -Fd they  
> are useful, and appear on the controlling terminal.
> 
> > For a proof-of-concept sort of thing, that might be reasonable though.
> 
> 
> It could be an additional clean-up once I'm done with the IPv6  
> support.  But I need to look at both implementations to see if one is  
> more appropriate for all of nfs-utils.
> 

FWIW, I don't have any particular attachment to either logging scheme.
It just seems like we could benefit from some standardization in this
area.

Not a high-priority item, but something to keep in mind if you poking
around in the code anyway.

-- 
Jeff Layton <jlayton@redhat.com>

  reply	other threads:[~2009-01-28 18:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 20:20 nfs-utils: support/nfs/rpcmisc.c Chuck Lever
2009-01-28 12:21 ` Steve Dickson
     [not found]   ` <49804DAC.2000309-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-01-28 17:59     ` Chuck Lever
2009-01-28 16:37 ` Jeff Layton
     [not found]   ` <20090128113749.7893533a-RtJpwOs3+0O+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-01-28 18:05     ` Chuck Lever
2009-01-28 18:17       ` Jeff Layton [this message]
     [not found]         ` <20090128131707.401de2f1-RtJpwOs3+0O+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-01-28 18:19           ` Chuck Lever

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=20090128131707.401de2f1@tleilax.poochiereds.net \
    --to=jlayton@redhat.com \
    --cc=SteveD@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=okir@suse.de \
    /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