From owner-freebsd-current Fri Jun 19 15:05:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14824 for freebsd-current-outgoing; Fri, 19 Jun 1998 15:05:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (root@mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14818 for ; Fri, 19 Jun 1998 15:05:19 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id SAA104182 for ; Fri, 19 Jun 1998 18:05:08 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <199806191851.LAA12551@usr06.primenet.com> References: <98Jun19.095515pdt.177515@crevenia.parc.xerox.com> from "Bill Fenner" at Jun 19, 98 09:55:00 am Date: Fri, 19 Jun 1998 18:08:54 -0400 To: current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Bogus errno twiddling by lstat... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One question I have is: Is there any reason that we must let lstat clobber the value of errno? Could we just add a few-line update somewhere which saves the value of errno on entry to lstat, and *if* no error occurs then reset errno before returning to the caller of lstat? Or does this start us down a path of having all kinds of system routines saving copies of errno? Note that I'm not really interested in whether lstat has the "right" to clobber errno. I'm just wondering what advantage there is in having it continue to clobber errno. --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message