Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Maybe you might want to give it a shot?
The latrace tracer is able to run a command and display its dynamic library calls
using a LD_AUDIT libc feature, available from libc version 2.4 onward. It is also
capable to measure and display various statistics of dynamic calls. See the section
called "DISCUSSION" for more details.
If the header file with functions' declarations is provided, latrace will display
functions's arguments. The header file file syntax is similar to the C language,
with several exceptions See the section called "HEADERS" for more details.
The latrace by default fully operates inside of the traced program. However another
"pipe mode" is available to move the main work to the tracer - the latrace binary.
See the section called "PIPE mode" for more details.
The latrace use is similar to strace(1) and ltrace(1).