Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Mar 2001 15:42:16 -0800
From:      Peter Wemm <peter@netplex.com.au>
To:        Martin Blapp <mb@imp.ch>
Cc:        Alfred Perlstein <bright@wintelcom.net>, "Andrey A. Chernov" <ache@nagual.pp.ru>, Daniel <freebsd@grunblatt.com.ar>, current@FreeBSD.ORG
Subject:   Re: [FIX] Re: CFS - Portmap 
Message-ID:  <200103222342.f2MNgGh76684@mobile.wemm.org>
In-Reply-To: <Pine.BSF.4.21.0103230028140.17221-100000@levais.imp.ch> 

next in thread | previous in thread | raw e-mail | index | archive | help
Martin Blapp wrote:
> 
> Ok,
> 
> here is what I found:
> 
> notes.ms, line 228
> 
> If your system does not support NFS mounts on ports other
> than 2049, add -DCFS_PORT=2049; you will not be able to simultaneously
> run the target system as an NFS server under this configuration.
> 
> cfs.h:#define CFS_PORT 2049
> nfsproto.h:#define      NFS_PORT 2049
> nfsproto.x:const NFS_PORT          = 2049
> 
> and then this code here:
> 
> if (!svc_reg(tp, NFS_PROGRAM, NFS_VERSION, nfs_program_2,
>        (port==2049? nc : NULL))) {
>          fprintf(stderr,"Can't register CFS NFS\n");
>                 exit(1);
> }
> 
> Cause the 5. argument (const char *nettype nc) is NULL in our case,
> svc_reg does not register cfs within rpcbind.
> 
> If you compile with -DCFS_PORT=2049, cfs works as normal.
> 
> I'm only thinking what is the right thing to do ...

Maybe it is ok as a short term workaround.

Breaking nfs from working on user defined ports is a step backwards and
should be fixed.  Lots of people run nfsd and cfsd at the same time.

> Martin
> 
> Martin Blapp, mb@imp.ch
> ------------------------------------------------
> Improware AG, UNIX solution and service provider
> Zurlindenstrasse 29, 4133 Pratteln, Switzerland
> Phone: +41 79 370 26 05, Fax: +41 61 826 93 01
> ------------------------------------------------
> 
> On Thu, 22 Mar 2001, Alfred Perlstein wrote:
> 
> > * Martin Blapp <mb@imp.ch> [010322 15:00] wrote:
> > > 
> > > Hi,
> > > 
> > > I see, seems that (port==2049? nc : NULL) has changed in some way.
> > > I'll fix that.
> > > 
> > > PS: let's change to private discussion and not cc current anymore.
> > 
> > Please don't, I'd like to understand what's going on here.
> > 
> > There's also a chance someone will jump in with the answer you're
> > looking for.
> > 
> > -- 
> > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]
> > Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/
> > 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 

Cheers,
-Peter
--
Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
"All of this is for nothing if we don't go to the stars" - JMS/B5


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200103222342.f2MNgGh76684>