From owner-freebsd-current Sun Jan 21 23:44: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id 6734037B69B for ; Sun, 21 Jan 2001 23:43:47 -0800 (PST) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by white.imgsrc.co.jp (8.11.2/8.11.0) with ESMTP id f0M7hjj26615; Mon, 22 Jan 2001 16:43:45 +0900 (JST) Date: Mon, 22 Jan 2001 16:43:43 +0900 Message-ID: <7m66j8t4k0.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Current Subject: Exit value of rtprio(1) User-Agent: Wanderlust/2.4.0 (Rio) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 13) (Crater Lake) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: multipart/mixed; boundary="Multipart_Mon_Jan_22_16:43:43_2001-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Multipart_Mon_Jan_22_16:43:43_2001-1 Content-Type: text/plain; charset=US-ASCII Manual page of rtprio(1) says it returns exit value 0 on success when PID is specified via argument. But current rtprio(1) returns 1 whether rtprio(2) is processed successfully or not. This patch seems to fix to return 0 on success as documented in manpage. Please let me know if it is wrong... I'll commit this in this week. -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project --Multipart_Mon_Jan_22_16:43:43_2001-1 Content-Type: application/octet-stream; type=patch Content-Disposition: attachment; filename="rtprio.diff" Content-Transfer-Encoding: 7bit Index: rtprio.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/rtprio/rtprio.c,v retrieving revision 1.8 diff -u -r1.8 rtprio.c --- rtprio.c 1999/08/28 01:19:49 1.8 +++ rtprio.c 2001/01/22 07:30:26 @@ -123,6 +123,7 @@ execvp(argv[2], &argv[2]); err(1, "%s", argv[2]); } + exit(0); } exit (1); } --Multipart_Mon_Jan_22_16:43:43_2001-1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message