Date: Tue, 11 Feb 2003 16:19:52 -0600
From: John Goerzen <jgoerzen@complete.org>
To: gopher@complete.org
Subject: [gopher] Re: Gopher novice question
Message-ID: <20030211221952.GA17086@wile.excelhustler.com>
References: <008701c2d1ca$43452880$01000001@tyamamot2w>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <008701c2d1ca$43452880$01000001@tyamamot2w>
User-Agent: Mutt/1.4i
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


This is a new bug as far as I know.  Can I get some information:

 * Linux distribution 
 * C library version
 * ncurses version

Also, can you try using a program such as strace or gdb to pinpoint the
problem location?  If you need help with them, let me know.

-- John

On Tue, Feb 11, 2003 at 09:36:28PM +0900, Taro Yamamoto wrote:
> 
> Dear guru,
>     I am a novice user of gopher. I recently started using a gopher client
> included in the gopher-3.0.5 distribution on my Linux machinie. Sometimes,
> when "accessing" a file on a different site, it hangs up. No real file
> transfer/reading occurs, and no communication errors are reported. This
> occurs on some objects. Not all objects have this symptom, but trying to
> accessing some objects fail with this symptom.
>     Typing Control-C makes it stop trying accessing the file, but it makes
> the program just hang up again.
>     It seems the hand-shaking doesn't continue well for such remote servers,
> while connection has been successful.
>     How can I avoid this, and how can I return from the hanging up state?
> 
> Thanks.
> 
> --Taro
> Tokyo
> (tyamamot@kt.rim.or.jp)
> 
> 
> 
>