Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Thanks for answering.
Unfortunately this is only about logging the programs that are manually started. However I am interested in all started programs, no matter by whom.
One idea that came up to me, was logging the results of ps -A. However if this is done only in a certain interval I would either miss a lot of small processes or get a damn big load of log-files with very few differences. My bash knowledge is extremely limited, is their a trivial solution to store only the lines of the ps -A output that haven't come up in the log so far? I notice several big "jumps", especially early, in the IDs in my ps -A output. Are those gaps reserved by some programs that could be run later or can I rely on new processes to always show up at the end of the output?
Is there a more elegant solution than using ps -A? The aim is still to log every process started, if it is started often, I want to log it every single time.
Thanks for answering.
Unfortunately this is only about logging the programs that are manually started. However I am interested in all started programs, no matter by whom.
One idea that came up to me, was logging the results of ps -A. However if this is done only in a certain interval I would either miss a lot of small processes or get a damn big load of log-files with very few differences. My bash knowledge is extremely limited, is their a trivial solution to store only the lines of the ps -A output that haven't come up in the log so far? I notice several big "jumps", especially early, in the IDs in my ps -A output. Are those gaps reserved by some programs that could be run later or can I rely on new processes to always show up at the end of the output?
Is there a more elegant solution than using ps -A? The aim is still to log every process started, if it is started often, I want to log it every single time.
You can write your own library, that has execve function with logging and then put name of this library into /etc/ld.preload file
This way (almost) any program will be executed with yours execve instead of system one.
Be sure to test your libraries well (with LD_PRELOAD) before adding it to /etc/ld.preload
Once your library name is here you will have a difficult time to get rid of it, if your library is buggy.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.