Date: Tue, 19 Mar 2002 12:30:57 -0600
Subject: [gopher] Re: Gopher on Mac OS X
Content-type: text/plain; charset=US-ASCII
Mime-Version: 1.0 (Apple Message framework v481)
From: Clint Paden <clintpaden@mac.com>
To: gopher@complete.org
Content-Transfer-Encoding: 8bit
In-Reply-To: <9B83B40E-3B53-11D6-BC1E-0003930BF072@complete.org>
Message-Id: <743A2946-3B67-11D6-B5AE-0030654C9DF2@mac.com>
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


>  I have
> been unable to figure out how to get the kind of log that you found
> below, a core dump, or anything like that.  Could you enlighten me?

John,
In the OS X environment, look in /Applications/Utilities and open 
Console. Look in the Preferences (under the Console menu). Click on the 
"Crashes" tab and then make sure the "Log crash information..." box is 
checked. Then, when gopher crashes (at least it did for me), there will 
be a file with the dump at ~/Library/Logs/gopherd.crash.log
There seems to be something logged in that file for almost every sever 
connection...odd, but I dont know enough about it to really say that.

Also, I dont know if this is the normal way for gopher to behave, but it 
seems only items with extensions that  have entries in the gopher.conf 
file will be served up by the server. A file with either an extension 
not in the file or no extension at all cause the directory to appear as 
if it is empty.

I will continue testing, and if I can be of any help to anyone, let me 
know. Have a nice day,

cLiNt