Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!crdgw1!sixhub!davidsen
From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr)
Newsgroups: comp.unix.sysv386
Subject: Re: ksh acting weird under SCO Unix
Message-ID: <2247@sixhub.UUCP>
Date: 7 Nov 90 01:52:31 GMT
References: <35582@cup.portal.com>
Reply-To: davidsen@sixhub.UUCP (bill davidsen)
Organization: *IX Public Access UNIX, Schenectady NY
Lines: 17

In article <35582@cup.portal.com> ts@cup.portal.com (Tim W Smith) writes:

| When I try to run it, it behaves very strangely.  As long as I
| only use shell builtin commands, all is well.  If I try to do
| things that run other programs, however, after anywhere from
| one to ten or so commands, the shell exits.  Worse, it kills
| everything in the process group.  This also happens right away
| if I try to run a command that is not found.

	[ more weirdness ]

Try this: "set +m" and see if all your problems go away.
-- 
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
    sysop *IX BBS and Public Access UNIX
    moderator of comp.binaries.ibm.pc and 80386 mailing list
"Stupidity, like virtue, is its own reward" -me