From: Steve Dickson <SteveD@redhat.com>
To: Chip Salzenberg <chip@pobox.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>, nfs@lists.sourceforge.net
Subject: Re: Re: Debian, SIGPIPE, "libnfsidmap", and init.d vs. umount
Date: Mon, 06 Dec 2004 14:39:35 -0500 [thread overview]
Message-ID: <41B4B577.3000009@RedHat.com> (raw)
In-Reply-To: <20041206020506.GJ6146@perlsupport.com>
Chip Salzenberg wrote:
>According to Neil Brown:
>
>
>>On Saturday December 4, chip@pobox.com wrote:
>>
>>
>>>Debian needs a bugfix release of nfs-utils, because of the SIGPIPE
>>>bug. This being my job, I figured I could grab the HEAD version of
>>>nfs-utils. And since the Debian sarge release is coming up soon (no,
>>>really), I hoped I'd find something unlikely to crash; instead I'm
>>>having difficulty with the build.
>>>
>>>
>>I use "./configure --disable-nfsv4 --disable-gss" but you might not
>>want to...
>>
>>
>
>Well, that could work, actually. Do you think that the changes since
>March 24 -- other than GSS and NFSv4 -- are valuable and safe?
>
>
Well I'm running the code with everything enabled and turned on,
for a while now.... things seem to be stable... but only time will
tell... ;-)
steved.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2004-12-06 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 22:15 Debian, SIGPIPE, "libnfsidmap", and init.d vs. umount Chip Salzenberg
2004-12-06 0:34 ` Neil Brown
2004-12-06 0:45 ` J. Bruce Fields
2004-12-06 2:02 ` Chip Salzenberg
2004-12-06 2:05 ` Chip Salzenberg
2004-12-06 2:29 ` Neil Brown
2004-12-06 19:39 ` 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=41B4B577.3000009@RedHat.com \
--to=steved@redhat.com \
--cc=chip@pobox.com \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
/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.