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
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

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