From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] nfs-utils 2 of 10 - Incorporate some clean up code from Ulrich Drepper
Date: Fri, 23 Sep 2005 12:56:15 -0400 [thread overview]
Message-ID: <433433AF.1040702@RedHat.com> (raw)
In-Reply-To: <1127490778.8328.6.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> Why not clean that up further by putting it into a simple library
> function that takes an argument consisting of the pipes you do not want
> it to close?
Good point... its just one things that appeared one day (Uli when
nuts and changed a bunch of system daemons) and since everything
seem to still work I never gave it a second thought...
Where would be the best place for this this new routine?
If we put the routine in libnfs.a, then both the
idmapd and svcgssd daemons would have to start
linking it which may or may not cause a problem..
Or maybe a new local library??
steved.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-09-23 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 14:44 [PATCH] nfs-utils 2 of 10 - Incorporate some clean up code from Ulrich Drepper Steve Dickson
2005-09-23 15:52 ` Trond Myklebust
2005-09-23 16:56 ` Steve Dickson [this message]
2005-09-23 18:23 ` Trond Myklebust
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=433433AF.1040702@RedHat.com \
--to=steved@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.