On Tue, Jul 26, 2005 at 01:11:04PM -0700, Jonathan Adams wrote:
> On Tue, Jul 26, 2005 at 11:34:09AM -0700, Jonathan Adams wrote:
> > On Tue, Jul 26, 2005 at 11:18:36AM -0700, J?rgen Keil wrote:
> > > I'm not 100% sure if it's still important to mark shared libraries
> > > with the execute bit with
On Tue, Jul 26, 2005 at 11:34:09AM -0700, Jonathan Adams wrote:
> On Tue, Jul 26, 2005 at 11:18:36AM -0700, J?rgen Keil wrote:
> > I'm not 100% sure if it's still important to mark shared libraries
> > with the execute bit with current Solaris 10 or OpenSolaris. It
> > seems the kernel is now usin
On Tue, Jul 26, 2005 at 11:18:36AM -0700, J?rgen Keil wrote:
> I'm not 100% sure if it's still important to mark shared libraries
> with the execute bit with current Solaris 10 or OpenSolaris. It
> seems the kernel is now using a vnode flag VVMEXEC to mark executable
> content, and this flag appea
It seems that with SunOS 5.6 & 5.7 it was important to mark the shared
libraries with
the executable bit, so that the "priority paging" feature wasn't confused.
See the section "How do I enable priority paging?" here:
http://www.sun.com/sun-on-net/performance/priority_paging.html#enable
Quote
> I've always wondered...why are shared libraries installed under *NIX
> operating systems with the executable bit set?
IIRC, the executable bit is used by the SunOS VM subsystem as a hint when
looking for
free memory. The VM subsystem prefers to free pure data pages (files without
the
executab
