From: Ben Leslie <benno@sesgroup.net>
To: nfs@lists.sourceforge.net
Subject: Re: mountd --no-tcp -p bugs?
Date: Fri, 14 Feb 2003 19:17:23 +1100 [thread overview]
Message-ID: <20030214191723.D26265@sesgroup.com.au> (raw)
In-Reply-To: <20030211002846.GC7774@retsil.sesgroup.com.au>
On Tue, 11 Feb 2003, Benno wrote:
> Hi all,
>
> I'm running into a couple of problems with mountd.
Hi again,
I haven't had any feedback on this email from a few days
ago. Is this not a bug and I'm missing something, or just
no one cares about bugs in client programs, or am I just being
impatient?
Thanks again,
Benno
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-02-14 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 0:28 mountd --no-tcp -p bugs? Ben Leslie
2003-02-14 8:17 ` Ben Leslie [this message]
2003-02-19 4:27 ` Neil Brown
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=20030214191723.D26265@sesgroup.com.au \
--to=benno@sesgroup.net \
--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.