[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Rule-list] subject: Rule-created nfsd problem
From: |
Richard Kweskin |
Subject: |
[Rule-list] subject: Rule-created nfsd problem |
Date: |
Sun, 18 Aug 2002 10:14:52 -0400 |
User-agent: |
KMail/1.4.1 |
Hello All
Once again installing rule using only the basic and networking options to
create a server for nfs. Whereas before it was with rh7.2 and an earlier
version of slinky, now it is Valhalla with slinky 029 on the same 586
referred to in earlier posts. Again the same results: the 586 fails to
work, but installing Valhalla with slinky 029 with the exact same
packages on my athlon works!
One other difference between the older 7.2 tests and these tests now is
that then the old 586 had 48MB memory instead of 16MB (but the rule
attempt still failed.) The 48MB allowed a text mode attempt using
ordinary anaconda making it possible for this complete newbie to choose
network options, installing lots of other rpm's resulting in a useable
nfs server on the 586. At the moment this extra memory is not available.
:(
Details:
1) openssh server in or out changes nothing, so only rule's basic +
networking options were used
2) invoking /etc/init.d/nfs start, "nfsd: cannot allocate 122880 bytes
for reply cache" and nfs daemon "fail" with "nfssvc: Address
already in use"
3) rpcinfo -p (afterwards) reveals mountd using port 2049
4) changing the order of invocation in the script, i.e. from "mountd
then nfsd" to "nfsd then mountd" reveals nfsd takes port 2049 while
mountd takes 2053 (if memory serves)
5) leaving the order of invocation as "mountd then nfsd" (original) but
imposing --port 2053 on mountd also allows nfsd to take port 2049
6) both of the two above hacks eliminate the nfs daemon "fail" with
"nfssvc: Address...." but don't help the reply cache problem and,
ultimately, attempts at accessing shares from elsewhere on the lan
remain foiled :(
7) exploring google's usenet search only turns up incompatiblity problems
or one attempt at someone's changing the limits on port delegation
Opinion:
while fun to try and hack, squashing "bugs", it seems that by installing
other packages, the "needs" that some older pc's seem to have with their
resources are at last fulfilled (details not nailed down, yet) whereas a
newer pc seems not to require them.
Anyone else want to try, meanwhile?
Richard
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Rule-list] subject: Rule-created nfsd problem,
Richard Kweskin <=