Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site hp-pcd.UUCP
Path: utzoo!linus!decvax!harpo!floyd!clyde!ihnp4!zehntel!hplabs!hp-pcd!hp-dcde!jack
From: jack@hp-dcde.UUCP
Newsgroups: net.bugs.uucp
Subject: reversed exitcode/signal in uuxqt - (nf)
Message-ID: <1991@hp-pcd.UUCP>
Date: Mon, 3-Oct-83 03:03:23 EDT
Article-I.D.: hp-pcd.1991
Posted: Mon Oct  3 03:03:23 1983
Date-Received: Thu, 6-Oct-83 06:50:44 EDT
Sender: notes_gateway@hp-pcd.UUCP
Organization: Hewlett-Packard, Fort Collins, CO
Lines: 23

#N:hp-dcde:16600001:000:637
hp-dcde!jack    Sep 30 09:27:00 1983

Our uuxqt is returning reversed status for a failed remote execution.

Here is a segment of code from uuxqt.c:

	ret = shio(buf, fin, dfile, NULL);
	exitsig = ret & 0377;
	exitcode = (ret>>8) & 0377;
	sprintf(retstat, "exit %d, signal %d", ret & 0377,
	  (ret>>8) & 0377);

Curiously enough, even though exitsig (what signal killed the process)
and exitcode (what parameter the process gave to exit)
are computed correctly, they are (incorrectly!) re-computed for the sprintf.

Hence, if a uux process exits with exit code 1, the message will say
"exit 0, signal 1" which is not the truth.

						-Jack Applin
						(hplabs!hp-dcd!jack)