From owner-freebsd-questions Mon Oct 5 09:56:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10270 for freebsd-questions-outgoing; Mon, 5 Oct 1998 09:56:37 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from mail.softcom.net (mail.softcom.net [209.160.160.4]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA10206 for ; Mon, 5 Oct 1998 09:56:23 -0700 (PDT) (envelope-from jon.ballard@usa.net) Received: from [209.160.171.105] by mail.softcom.net (NTMail 3.03.0017/7.aav0) with ESMTP id ca145862 for ; Mon, 5 Oct 1998 09:55:48 -0700 Message-ID: <3618FC77.7AD84B06@usa.net> Date: Mon, 05 Oct 1998 10:06:02 -0700 From: Jon Ballard Organization: Cybertronix X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG Subject: process execution Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a function call from C, that is like yield() to threads, that would hand the execution to the next process? I remember something like this on older Sys V clones but can't remember what it is. ("break()" syscall?) I need to preform REAL TIME execution. An example would be like: while(true) { idle = true; if(condition1) { idle = false; ... } if(condition2) { idle = false; ... } .... if(idle) { hand execution to other processes } } The process would not need it's full time-slice if the conditions would cause an idle state. The process would not have any open file descriptors. It is dealing stricly with shared memory. So the conditions would be testing for flags set in the shared memory. Using a timer is not ok. The goal is to have the process strictly in user time and no system time if idle. It's been 10 years since I've done such a thing and can't remember what that function is... (yes I've grep'ed the manuals) Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message