From: Bernd Schubert <bernd-schubert@web.de>
To: nfs@lists.sourceforge.net
Subject: Re: ANNOUNCE: nfs-utils 1.0.7-pre2
Date: Fri, 10 Dec 2004 14:20:06 +0100 [thread overview]
Message-ID: <200412101420.06172.bernd-schubert@web.de> (raw)
In-Reply-To: <16825.223.924965.582375@cse.unsw.edu.au>
On Friday 10 December 2004 02:50, Neil Brown wrote:
> I have made available a second pre-release of nfs-utils 1.0.7.
>
> It can be downloaded from
> http://sourceforge.net/project/showfiles.php?group_id=3D14
> or
> http://www.{countrycode}.kernel.org/pub/linux/utils/nfs/
>
> This release adds some statd fixes and a couple of other small bug fixes,
> and also gets ./configure to complain if libnfsidmap or libevent aren't
> installed (unless --disable-nfsv4 is selected).
> README also says where to get these libraries from.
Well, it still complains with --disable-nfsv4:
svcgssd_proc.c:47:22: nfsidmap.h: No such file or directory
make[4]: *** [dep] Error 1
make[3]: *** [dep] Error 2
make[2]: *** [dep] Error 2
Should the configure script assume '--disable-gss' when --disable-nfsv4 is=
=20
given?=20
>
> I still hope to put this out as a final 1.0.7 before Christmas.
> Having lots of people say "Yes, I've tried it, and it works OK" would
> make a great Christmas present :-)
>
Well, with --disable-nfsv4 --disable-gss and without '--enable-secure-statd=
'=20
the statd seems to work fine. As I posted a very long time ago, we are seei=
ng=20
messages like this
lockd: cannot monitor 129.206.21.200
lockd: failed to monitor 129.206.21.200
statd: server localhost not responding, timed out
nsm_mon_unmon: rpc failed, status=3D-5
lockd: cannot monitor 129.206.21.200
lockd: failed to monitor 129.206.21.200
very often if '--enable-secure-statd' is enabled. This also causes much=20
trouble to other services as portmap, ssh, nis, cron, etc. and makes them=20
also crash (not so good as we can't reboot the systems).
Unfortunately this also happens randomly to one/some of our clients rather=
=20
often since we switched to a new server in summer, don't know the reasons=20
yet.
I will now try to enable secure-statd, compiling with debug options and hop=
e=20
the statd core files will help to understand the problem. Though, maybe tho=
se=20
problems are already fixed?
Cheers,
Bernd
=2D-=20
Bernd Schubert
Physikalisch Chemisches Institut / Theoretische Chemie
Universit=E4t Heidelberg
INF 229
69120 Heidelberg
e-mail: bernd.schubert@pci.uni-heidelberg.de
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-12-10 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 1:50 ANNOUNCE: nfs-utils 1.0.7-pre2 Neil Brown
2004-12-10 10:12 ` Olaf Kirch
2004-12-10 10:34 ` Neil Brown
2004-12-10 13:20 ` Bernd Schubert [this message]
2004-12-10 14:30 ` J. Bruce Fields
2004-12-17 4:00 ` Neil Brown
2004-12-15 18:30 ` Paul Clements
2004-12-15 19:10 ` Robert Schwebel
2004-12-15 19:37 ` J. Bruce Fields
2004-12-16 9:14 ` Robert Schwebel
2005-01-13 20:34 ` J. Bruce Fields
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=200412101420.06172.bernd-schubert@web.de \
--to=bernd-schubert@web.de \
--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.