From owner-freebsd-current Thu Mar 22 15:32:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 836FC37B71B for ; Thu, 22 Mar 2001 15:32:18 -0800 (PST) (envelope-from mb@imp.ch) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id f2MNW4p31049; Fri, 23 Mar 2001 00:32:04 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Fri, 23 Mar 2001 00:33:28 +0100 (CET) From: Martin Blapp To: Alfred Perlstein Cc: "Andrey A. Chernov" , Daniel , current@FreeBSD.ORG Subject: Re: [FIX] Re: CFS - Portmap In-Reply-To: <20010322152422.K9431@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 ... 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 [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