Re: Tru64 compile/link problem

From: Jeff Donsbach (jeff.donsbach_at_hp.com)
Date: 11/20/03

  • Next message: David Butenhof: "Re: Thread safe malloc in Tru64?" 
    Date: Thu, 20 Nov 2003 20:24:14 GMT

    Ann Majeske wrote:
    > "Pablo Endres" <pablo_endres@digitel.com.ve> wrote in message
    > news:336f1a66.0310171148.11eeb41e@posting.google.com...
    >
    >> You compile the software and place it first in the library_path. All
    >> it does is log all the calls to execv and execve and then call the
    >> correct symbol in the C library.
    >
    >
    > If all you're trying to do is find a way to log execv and execve calls,
    > why don't you look at the Audit subsystem? Once it is built into
    > your system you can use it to log any syscall use on your system,
    > as well as other security related things like logins. See the Security
    > Manual for more information.
    >

    This also looks like a very good candidate for an ATOM tool. And a
    pretty simple one at that. 

    --
Jeff Donsbach
Developer Resource Center	T/(978) 506-5227
HP Partner Technical Services	jeff.donsbach@hp.com
  • Next message: David Butenhof: "Re: Thread safe malloc in Tru64?"