NetNews Usenet Archive 1993 #3/NN_1993_3.iso/spool/comp/infosyst/gopher/2111

Internet Message Format | 1993-01-28 | 1.6 KB

Path: sparky!uunet!charon.amdahl.com!pacbell.com!decwrl!sdd.hp.com!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!The-Star.honeywell.com!umn.edu!news2.cis.umn.edu![e-mail]
From: [e-mail] (paolo petta)
Message-ID: <[e-mail]>
Subject: [Q] gopherd hangups due to logfile handling... solved?
Original-To: [e-mail]
Date: Tue, 26 Jan 1993 20:13:04 +0100
X-Mailer: ELM [version 2.3 PL11]
Newsgroups: comp.infosystems.gopher
Distribution: comp
Sender: [e-mail]
Approved: [e-mail]
Lines: 21

My apologies in case this issue was already discussed/solved..

Even in the 1.11 version, gopherd "hangs up" from time to time at
our site (gopher.ai.univie.ac.at (a sun 4c)):
the symptoms are old "gopherd"s left around that contribute a *lot*
to the system load without doing anything visibly useful.

After killing these "zombie" gopherd processes, it also somtimes
happens that new invocations of gopher get stuck after retrieving the
root directory (i.e. the "wheel" "spins" for some time at the bottom
left) but before displaying it. A bit investigation identified the
logfile (specified with the "-l" option) being the culprit (i.e.
renaming/disposing the old logfile "fixed" the problem).

I would be extremely grateful for any helpful comments,

paolo
--
paolo petta                                            [phone](Tel)
Austrian Research Inst. for Artificial Intelligence    [phone](Fax)
Schottengasse 3, A-1010 Vienna, Austria, Europe     [e-mail]