On 20 Jul 93 19:49:44 GMT, aehall@calvin.seattleu.edu (OUTTA HERE!) said:

quoted text
> I having an extremely problem:

quoted text
> I'm running seyon just fine when, about five minutes into a call,
> I get the following message:

quoted text
>>> Error: Killed by signal 11.
>>> Notice: Debugging info: pid=1870..
>>> Notice: Press any key to exit.

quoted text
> Then I press a key, and it exits.

quoted text
> I've waited to press the key and done a ps and found that 1870 is the
> pid of seyon itself.  That's about all I can figure out.

quoted text
> I thought my uugetty might be killing seyon, but I disabled uugetty
> and seyon was still being killed by someone.

quoted text
> Which signal is 11?

Quick hint - 'kill -l' lists all the signal numbers.

I think that 11 is a segmentation fault, unfortunately.  You might be
able to cure it by recompiling a newer version of Seyon - version
2.14b is on sipb.mit.edu in /pub/seyon.  It works great for me,
although it does do nasty things with the X bell - I just commented
out those lines.

Cheers,
 Stephen.
---
Stephen Tweedie <sct@dcs.ed.ac.uk>   (JANET: sct@uk.ac.ed.dcs)
Department of Computer Science, Edinburgh University, Scotland.