Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!ames!amdahl!nsc!taux01!cjosta From: cjosta@taux01.UUCP (Jon Sweedler) Newsgroups: comp.unix.questions Subject: Re: "Deep Background" applications (One of those days...) Message-ID: <781@taux01.UUCP> Date: 26 Jun 88 11:56:25 GMT References: <649@necis.UUCP> <29500025@urbsdc> <11019@cgl.ucsf.EDU> <2772@ttrdc.UUCP> <779@taux01.UUCP> <780@taux01.UUCP> Reply-To: cjosta@taux01.UUCP (Jon Sweedler) Organization: National Semiconductor (Israel) Ltd. Lines: 27 In article <780@taux01.UUCP> cjosta@taux01.UUCP (Jon Sweedler) writes: >In article <779@taux01.UUCP> cjosta@taux01.UUCP (Jon Sweedler) writes: >>man page, running a process with a priority of 20 (PRIO_MAX really) will > ^^^^^^^^ >Oops. This should be PRIO_MIN. And also, under BSD 4.2, PRIO_MIN is >set to 19. Under BSD 4.3 it is 20. Sorry for the multiple postings, but I think I have it right this time... This is kind of bizarre, but what can you expect from Unix? Under true BSD 4.3, PRIO_MAX is defined as 20 and PRIO_MIN is defined as -20. Regular users can "nice" their processes from 0 to 20. Under two BSD 4.2 workalikes (DYNIX and Ultrix) that we have here, PRIO_MAX is defined as -20 and PRIO_MIN is defined as 20 (i.e. backwards from BSD 4.3 and thus the reason for my confusion). Regular users can "nice" their processes from 0 to 19 (despite the fact that in the Ultrix man page for "nice" it says from 0 to 20). "Standards are wonderful, there are so many to chose from..." -- someone -- Jon Sweedler ===== National Semiconductor (Israel) UUCP: {ames!amdahl,hplabs,sun,decwrl}!nsc!taux01!cjosta Domain: cjosta@taux01.nsc.com Paper: 6 Maskit st., P.O.B. 3007, Herzlia B 46104, Israel