Received: with ECARTIS (v1.0.0; list gopher); Sun, 16 Jan 2005 21:32:42 -0600 (CST) Received: from mx.freeshell.org ([192.94.73.21] helo=sdf.lonestar.org) by glockenspiel.complete.org with esmtp (Exim 4.34) id 1CqNd8-0003wk-RE for gopher@complete.org; Sun, 16 Jan 2005 21:32:41 -0600 Received: from sdf.lonestar.org (IDENT:beaker@otaku.freeshell.org [192.94.73.2]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id j0H3W8k1023321 for <gopher@complete.org>; Mon, 17 Jan 2005 03:32:08 GMT Received: (from beaker@localhost) by sdf.lonestar.org (8.12.10/8.12.8/Submit) id j0H3W8sg005950 for gopher@complete.org; Sun, 16 Jan 2005 19:32:08 -0800 (PST) Date: Sun, 16 Jan 2005 19:32:08 -0800 From: =?iso-8859-1?Q?Jeff=5FW?=<beaker@freeshell.org> To: gopher@complete.org Subject: [gopher] UMN gopherd not logging w/ "-I" Message-ID: <41eb31b8.cZS6OLmk/RfoiUy1%beaker@freeshell.org> User-Agent: nail 11.17 11/18/04 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-Spam-Status: No (score 0.3): NO_REAL_NAME=0.285 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Sun, 16 Jan 2005 21:32:41 -0600 X-archive-position: 1004 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: beaker@freeshell.org Precedence: bulk Reply-to: gopher@complete.org List-help: <mailto:ecartis@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Ecartis version 1.0.0 List-Id: Gopher <gopher.complete.org> X-List-ID: Gopher <gopher.complete.org> List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe> List-owner: <mailto:jgoerzen@complete.org> List-post: <mailto:gopher@complete.org> List-archive: <http://www.complete.org/mailinglists/archives/> X-list: gopher

I know this thing is considered obsolete but ...

I thought I'd try running gopherd out of inetd just to see what the load difference would be. gopherd was getting started with the following options:

# gopherd -Ic -l /var/log/gopherlog -u furry /home/furry

I was unsure about NetBSD's inetd limitations on the number of command words allowed so I tried the above with an externally called script; same results. inetd.conf entry was taken directly out of the gopherd man page.

Oh yeah; Version: U of Minnesota Unix 3.0 pl2

Testing showed that while gopherd got started and killed ok, the /var/log/gopherlog file never got created and, even when I created it, it never got wrote to. Is this normal behavor for gopherd? Dropping the "-I" fixes the logging problem, so I'm fairly confident that there were no write access issues.

Cheers, Jeff