From: Mike Frysinger <vapier@gentoo.org>
To: nfs@lists.sourceforge.net
Subject: Re: [NFS] exportfs -r: segfault with sec= option
Date: Sun, 30 Dec 2007 15:16:34 -0500 [thread overview]
Message-ID: <200712301516.35053.vapier@gentoo.org> (raw)
In-Reply-To: <200712301259.29484.vapier@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 386 bytes --]
On Sunday 30 December 2007, Mike Frysinger wrote:
> while testing other things, i was toying with /etc/exports and inserting
> bogus lines. i found that this simple one makes exportfs segfault:
> /mnt 192.168.0.0(sec=)
> then just run `exportfs -r`
>
> this version of nfs-utils has gss disabled ...
scratch this ... i needed the post-1.1.1 fix for segfaults on amd64 with xlog
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
[-- Attachment #2: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- Attachment #3: Type: text/plain, Size: 362 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
prev parent reply other threads:[~2007-12-31 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 17:59 [NFS] exportfs -r: segfault with sec= option Mike Frysinger
2007-12-30 20:16 ` Mike Frysinger [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=200712301516.35053.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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.