Date: Mon, 5 May 2003 18:00:00 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Kirk McKusick <mckusick@beastie.mckusick.com> Cc: Brian Buhrow <buhrow@lothlorien.nfbcal.org> Subject: Re: Access times on executables (kern/25777) Message-ID: <20030505080000.GA1595@cirb503493.alcatel.com.au> In-Reply-To: <200305042351.h44Np2Th017215@beastie.mckusick.com> References: <20030504110643.Q1248@gamplex.bde.org> <200305042351.h44Np2Th017215@beastie.mckusick.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, May 04, 2003 at 04:51:02PM -0700, Kirk McKusick wrote: >OK, so how about instead of use VOP_SETATTR, we just try to VOP_READ >one byte of data. ... >It has the drawback of requiring that the file be readable though most >executables are set to be readable. I think it's common for set[gu]id executables not to be readable. Though, looking at my systems, I can only find xterm (from 4.3.0) and Xwrapper (from 3.3.6) that restrict read access more than execute access. Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030505080000.GA1595>