From: Neil Brown <neilb@suse.de>
To: Bernd Schubert <bernd-schubert@gmx.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: RELEASE CANDIDATE - nfs-utils-1.1.0-rc1
Date: Fri, 30 Mar 2007 12:19:49 +1000 [thread overview]
Message-ID: <17932.29637.650203.597630@notabene.brown> (raw)
In-Reply-To: message from Bernd Schubert on Thursday March 29
On Thursday March 29, bernd-schubert@gmx.de wrote:
> On Thursday 29 March 2007 06:12:45 Neil Brown wrote:
> > I've finished fiddling with statd, and am happy with mount.nfs now, so
> > it must be time for the first release candidate for nfs-utils-1.1.0.
> >
>
> While you are working on statd, maybe you can look into a problem I recently
> had?
> After the update from Debian Sarge to Etch, the update scripts dumped the
> current portmapper status to read them in after the portmap restart. Well,
> this was an update of a chroot and the portmapper never got restartet on the
> server and so also the dump file wasn't deleted.
> The diskless clients using this chroot read in the dump file, but also
> couldn't delete it, since it was located in a read-only nfs-export (*).
>
> The problem was statd, the dumpfile said that statd is running on a port <
> 1024, but since rpc.statd as user statd is not allowed to use ports <1024, it
> refused to start up at all.
>
> Well, while this clearly can and should be solved by removing the stale
> portmapper dump file, maybe there's also a solution for rpc.statd?
rpc.statd used to drop root privilege before binding the port to
listen on. This is fixed in 1.1.0, so that little part of your
problem should go away.
NeilBrown
>
>
> Thanks,
> Bernd
>
> PS: (*) Somewhere in /var, which will become writable after a union mount,
> which will be done after the start-up of portmap.
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-03-30 2:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 4:12 RELEASE CANDIDATE - nfs-utils-1.1.0-rc1 Neil Brown
2007-03-29 8:44 ` Jan Rekorajski
2007-03-29 9:31 ` Neil Brown
2007-03-29 12:44 ` Jan Rekorajski
2007-03-29 14:20 ` Trond Myklebust
2007-03-29 16:35 ` J. Bruce Fields
2007-03-29 16:45 ` Talpey, Thomas
2007-03-29 14:24 ` Trond Myklebust
2007-03-29 14:30 ` Talpey, Thomas
2007-04-01 12:16 ` Frank van Maarseveen
2007-04-01 23:35 ` Neil Brown
2007-04-01 12:04 ` Frank van Maarseveen
2007-03-29 9:51 ` Bernd Schubert
2007-03-30 2:19 ` Neil Brown [this message]
2007-03-30 10:44 ` Bernd Schubert
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=17932.29637.650203.597630@notabene.brown \
--to=neilb@suse.de \
--cc=bernd-schubert@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox