> Date: Fri, 10 Aug 2001 23:03:24 -0400 > From: Wayne Topa <[EMAIL PROTECTED]> > Subject: Re: new install nfs not working > To: debian-user@lists.debian.org > Resent-Date: Sat, 11 Aug 2001 03:31:17 -0700 (PDT) > X-Envelope-Sender: [EMAIL PROTECTED] > Mail-Followup-To: debian-user@lists.debian.org > In-Reply-To: <[EMAIL PROTECTED] <[EMAIL PROTECTED]> > User-Agent: Mutt/1.3.18i > Resent-Message-ID: <[EMAIL PROTECTED]> > Resent-From: debian-user@lists.debian.org > X-Mailing-List: <debian-user@lists.debian.org> archive/latest/163360 > X-Loop: debian-user@lists.debian.org > Precedence: list > Resent-Sender: [EMAIL PROTECTED] > X-Mozilla-Status2: 00000000 > > > Subject: new install nfs not working > Date: Fri, Aug 10, 2001 at 10:20:04AM -0700 > > In reply to:[EMAIL PROTECTED] > > Quoting [EMAIL PROTECTED]([EMAIL PROTECTED]): > > uname: Debian of course. > > Linux 2.4.5 #1 Sat Jun 16 07:33:46 PDT 2001 i686 unknown > > > > Hello all. Just installed nfs using apt-get but haven't got it to work > > yet -----------------------------------------<snip>
> I don't. > No expert on NLS but I have it working so I'll try to help -----------------------<snip> Ok it took awhile for me to get and reply to this message because fetchmail went out on me. I think it is related to the nfs-server packages I installed, in particular 'bwnfsd'. First the command: $ fetchmail -v -v -L mytestlogfile produces nothing. No data what so ever to look at. So trying to remove fetchmail via 'apt-get remove' 'depkg --purge' and trying to reinstall produces errors that are reliant on bwnfsd. Then trying to remove and reinstall bwnfsd all produces the same error, which is: -------------- Starting BWNFS daemon: rpc: RPC: Timed out dpkg: error processing bwnfsd (--configure): subprocess post-installation script returned error exit status 255 Errors were encountered while processing: bwnfsd E: Sub-process /usr/bin/dpkg returned an error code (1) ---------------- why it wants to start the BWNFS daemon when I want to remove bwnfsd and remove fetchmail I've not a clue. Searching I was able to find an email with the same problem at: http://lists.debian.org/debian-security-0103/msg00039.html but cannot find a follow up to it. I'm now tying to get in the post-installation script and see if I can figure out error 255 and or logs but I am clumsy at this. Any help on how to diagnos this? Much thanks in advance.