Bug in initializing epoch's x-connection

Thread View: gnu.epoch.misc

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Philip Ross Fri, 12 Jun 1992 13:27

#1359

Author: Philip Ross
Date: Fri, 12 Jun 1992 13:27

48 lines
2751 bytes

We have been experiencing a problem with the current release of epoch,
4.0 Patchlevel 2, running on a SUN IPC with SunOS 4.1.1.  

When using an IBM PC clone running an X emulator there is a limited
number of sockets available.  If an attempt is made to start an epoch client
when this limit is exceeded, epoch fails to initialise correctly and
goes into a state continuously using a large amount of CPU time.
This rogue epoch is not killed when the user logs off and remains
until a 'kill' signal is explicitly sent to it.

After some investigation the problem appears to be related to the
error handling in routine x_term_init() before calling
x_init_display().  The default IOErrorHandler is set to XIgnoreError;
consequently when epoch fails to make a successful connection it
appears to ignore the error (!) and goes into the compute loop.  As a
work around to the problem I have moved the line 

XSetIOErrorHandler (handler); 

to be immediately after the line

x_init_display ();

I am unsure if this is a sensible fix or indeed why the
IOErrorHandling is set to ignore system errors.  I would be grateful
if somebody who knows more about the workings of X and its interaction
with epoch would let me know.


Philip Ross    email: ross%athena@uk.ac.aberdeen
                  or  p.ross@uk.ac.aberdeen

Computer Officer,
University of Aberdeen,
Scotland.



/----------------------------------------------------------------------------\
| Philip Ross, Computer Officer | email: ross%athena@UK.AC.ABERDEEN          |
| Dept. Bio-Medical Physics     |    or  p.ross@uk.ac.aberdeen               |
| University of Aberdeen        |                                            |
| Foresterhill                  | [+44]-224-685645               (Fax)       |
| Aberdeen.  AB9 2ZD            | [+44]-224-681818 x53210        (Voice)     |
|----------------------------------------------------------------------------|
| 3 is not equal to 2, not even for large values of 2.                       |
\----------------------------------------------------------------------------/

Re: Bug in initializing epoch's x-connection

#1362

Author: Allen M. Cohen
Date: Sat, 13 Jun 1992 00:36

9 lines
1195 bytes

When will epoch work from an X-Terminal that's connected to a 486 machine
using ISC 3.0?  Currently it immediately crashes!

Does anybody have any examples of how to use zones?
-- 
<> Allen M. Cohen                  Internet:  amc@wlv.imsd.contel.com       <>
<> 1853 Stonesgate St.             UUCP:      elroy.Jpl.Nasa.Gov!agi0!allen <>
<> Westlake Village, Ca. 91361     Telephone: (805) 498-9611 ext. 195       <>
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads