rpc.bootparamd oddness in 4.1

[Ken Hughes]

first, i apologize for the lowercase post; i've a sprained wrist...

[[Converted by the usual anti-all-lowercase-editor :) -bdg]]

We have a sparcserver 390 running 4.1 here. A few weeks ago we temporarily
installed some 4/65 on it while another server was down, using the
add_client scripts. When the other server was back up, we removed them
with the remove script. Now, however, the Sparc rpc.bootparamd still
responds to the nfs bootparam requests even though the /etc/bootparams and
bootparams YP map show no mention of the clients. This happens even after
complete reboots of the server. If we kill or stop rpc.bootparamd while
the clients boot everything is fine. Has anyone seen this or have a clue
to what we may have overlooked?

Ken Hughes  (hughes at sol.csee.usf.edu)
FT-Ph D student, PT-ex-sysadm
Dept of Comp Sci and Eng
University of South Florida