Subject: lib/10275: TI-RPC failure without /etc/netconfig is obtuse
To: None <gnats-bugs@gnats.netbsd.org>
From: Jason R Thorpe <thorpej@frau-farbissina.shagadelic.org>
List: netbsd-bugs
Date: 06/03/2000 21:46:16
>Number: 10275
>Category: lib
>Synopsis: TI-RPC failure without /etc/netconfig is obtuse
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: lib-bug-people
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Sat Jun 03 21:47:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:
>Release: Sat Jun 3 21:34:02 PDT 2000
>Organization:
6th and Hugo Software
>Environment:
System: NetBSD frau-farbissina 1.4Z NetBSD 1.4Z (FRAU-FARBISSINA) #21: Sat Jun 3 20:05:37 PDT 2000 thorpej@frau-farbissina:/u2/netbsd/src/sys/arch/alpha/compile/FRAU-FARBISSINA alpha
>Description:
The new TI-RPC code works on LP64 systems (albiet lint(1) complains
about several things while building it), tho at first I thought it
didn't, because I had forgotten to install /etc/netconfig.
It might be nice if when /etc/netconfig is missing, instead
of:
frau-farbissina:thorpej 38$ su
clntudp_create: RPC: Unknown protocol
clnttcp_create: RPC: Unknown protocol
clntudp_create: RPC: Unknown protocol
clnttcp_create: RPC: Unknown protocol
clntudp_create: RPC: Unknown protocol
clnttcp_create: RPC: Unknown protocol
su: who are you?
A warning like:
WARNING: /etc/netconfig missing
could be issued, perhaps even with a fallback to some "reasonable"
set of defaults (tho if the warning were there, it would be
immediately obvious how to solve the problem).
Anyhow, it took me by surprise, so I could imagine it could
take others by surprise, too.
>How-To-Repeat:
Attempt to use TI-RPC with a missing /etc/netconfig.
>Fix:
Not provided.
>Release-Note:
>Audit-Trail:
>Unformatted: