From owner-freebsd-current  Thu May 28 14:51:45 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA03947
          for freebsd-current-outgoing; Thu, 28 May 1998 14:51:45 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03931
          for <current@freebsd.org>; Thu, 28 May 1998 14:51:38 -0700 (PDT)
          (envelope-from dufault@hda.hda.com)
Received: (from dufault@localhost)
	by hda.hda.com (8.8.5/8.8.5) id RAA21367;
	Thu, 28 May 1998 17:27:33 -0400 (EDT)
From: Peter Dufault <dufault@hda.com>
Message-Id: <199805282127.RAA21367@hda.hda.com>
Subject: Re: cdrecord trouble on currnet
In-Reply-To: <199805281948.MAA01246@dingo.cdrom.com> from Mike Smith at "May 28, 98 12:48:57 pm"
To: mike@smith.net.au (Mike Smith)
Date: Thu, 28 May 1998 17:27:31 -0400 (EDT)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> It checks _POSIX_PRIORITY_SCHEDULING at build time.  
 
That's understandable, then.

> Can you give an example of the correct mechanism for using sysconf() to 
> determine the availability of the scheduler?  I'll fix it in the 
> updates I'm working on.

    if (sysconf(_SC_PRIORITY_SCHEDULING) == -1) {
        if (errno != 0) {
            /* This isn't valid:
             */
            err(EX_OSERR, "sysconf(_SC_PRIORITY_SCHEDULING)");
        }
        else {
            errx(EX_UNAVAILABLE,
            "No run-time support for POSIX priority scheduling");
        }
    }

Peter

-- 
Peter Dufault (dufault@hda.com)   Realtime development, Machine control,
HD Associates, Inc.               Safety critical systems, Agency approval

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message