Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.411 (Entity 5.404) X-RT-Original-Encoding: iso-8859-1 Content-Length: 1846 From bjaspan@MIT.EDU Mon Dec 2 13:26:09 1996 Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by rt-11.MIT.EDU (8.7.5/8.7.3) with SMTP id NAA11984 for ; Mon, 2 Dec 1996 13:26:08 -0500 Received: from DUN-DUN-NOODLES.MIT.EDU by MIT.EDU with SMTP id AA08716; Mon, 2 Dec 96 13:26:07 EST Received: by DUN-DUN-NOODLES.MIT.EDU (5.x/4.7) id AA23159; Mon, 2 Dec 1996 13:26:05 -0500 Message-Id: <9612021826.AA23159@DUN-DUN-NOODLES.MIT.EDU> Date: Mon, 2 Dec 1996 13:26:05 -0500 From: bjaspan@MIT.EDU Reply-To: bjaspan@MIT.EDU To: krb5-bugs@MIT.EDU Subject: document error string -> file identity X-Send-Pr-Version: 3.99 >Number: 269 >Category: krb5-doc >Synopsis: document error string -> file identity >Confidential: no >Severity: serious >Priority: medium >Responsible: krb5-unassigned >State: open >Class: sw-bug >Submitter-Id: unknown >Arrival-Date: Mon Dec 02 13:27:01 EST 1996 >Last-Modified: >Originator: Barry Jaspan >Organization: mit >Release: 1.0-development >Environment: System: SunOS DUN-DUN-NOODLES 5.4 Generic_101945-37 sun4m sparc >Description: Steve Webster makes the good point that it is very difficult for a novice admin to tell which file is missing or wrong when any of a large number of error messages are generated by Kerberos programs. He suggests a table such as >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: >> If you see and error the missing file is probably >> ----------------- ---------------------------- >> while setting active database /foo/bar >> while initializing database /baz/bletch >> opening policy database ... >> ... Probably this should be in each program's manual page, but it could also be in the texinfo files.