Xref: utzoo comp.mail.elm:471 comp.unix.xenix:2013
Path: utzoo!utgpu!water!watmath!clyde!att-cb!osu-cis!tut.cis.ohio-state.edu!uwmcsd1!marque!uunet!peregrine!ccicpg!turnkey!stanton!donegan
From: donegan@stanton.TCC.COM (Steven P. Donegan)
Newsgroups: comp.mail.elm,comp.unix.xenix
Subject: Re: Elm and XENIX
Summary: SIGHUP and elm 1.7
Message-ID: <18@stanton.TCC.COM>
Date: 16 Apr 88 02:40:09 GMT
References: <10861@codas.att.com> <150@amcad.UUCP> <13@stanton.TCC.COM> <181@ists>
Organization: Stanton Public Domain Systems, Stanton, Ca.
Lines: 20

In article <181@ists>, mike@ists (Mike Clarkson) writes:
> In article <13@stanton.TCC.COM>, donegan@stanton.TCC.COM (Steven P. Donegan) writes:
> > 
> > I have elm 1.7 working quite well on my SCO 2.2.1 (286) system. The only
> > problems I have noted so far are:
> > 
> > 2) If a user is in elm in some functions and gets disconnected the session
> >    remains running - SIGHUP appears to have been defused.

In one of it's source modules elm 1.7 traps signal SIGHUP, SCO Professional
and SCO FOXPLUS also have this 'feature'. I expect it has to do with some
misguided sense of file integrity. When I have tested my 'fix' to the source
I will be happy to post. The problem with elm 1.7 was not reported by me,
but by my local xenix guru, news feed and friend Jack Vogel of Turnkey
Computer Consultants.
-- 
Steven P. Donegan
Sr. Telecommunications Analyst
Western Digital Corp.
donegan@stanton.TCC.COM