From owner-freebsd-hackers Mon Jul 13 07:22:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06309 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 07:22:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06302 for ; Mon, 13 Jul 1998 07:22:41 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id QAA00975; Mon, 13 Jul 1998 16:19:22 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id KAA04341; Mon, 13 Jul 1998 10:07:32 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807130807.KAA04341@semyam.dinoco.de> To: "Allen Smith" Subject: Re: Best means of telling if a proc is still around? In-reply-to: Your message of "Sun, 12 Jul 1998 22:45:30 EDT." <9807122245.ZM24864@beatrice.rutgers.edu> Cc: seggers@semyam.dinoco.de, freebsd-hackers@FreeBSD.ORG Date: Mon, 13 Jul 1998 10:07:31 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi. What's the best fast means of telling if a reference to a proc > structure is still valid? I'm needing this for the work on privileges > that I'm doing. (Specifically, there are circumstances where an action > initiated by a process that then exits may be a privileged one, and > may not get to the point of checking the privileges before the exit > takes place.) Use at_exit(9) to know when it exits. If it is important to you an at_exec(9) might be needed, too. The latter does not exist, yet. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message