* Darren J Moffat <[email protected]> [2009-08-24 09:28]: > does $VEREXEC_ALTDIR have to be fully populated with everything from > /etc/verexec.d ? Or do we search $VEREXEC_ALTDIR first then search > /etc/verexec.d ? Is it worth $VEREXEC_ALTDIR being a list (':' > separated) ?
At present, it would need to be fully populated. It's simple enough to make verexec(1) fall back to the default if a specific argv[0] can't be found. I'd prefer not to make it $PATH-like, but I guess we could. For either case, we'll need to have VEREXEC_DEBUG so that an administrator can easily see the fallback cases. - Stephen -- [email protected] http://blogs.sun.com/sch/ _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
