Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'd like to start keeping track of which binaries users run on our Linux cluster. I'd like log the results on each node, and then aggregate them to find the total. I'd like to eventually to get to the point where I can run a report at the end of the month and see that /usr/bin/foo was run 9000 times.

My question is about the logging aspect. What facility is best to achieve this? process accounting? auditd?

Specifically I'd like the log to keep track of the path to each executable run, and how often it was executed.

share|improve this question
up vote 2 down vote accepted

Years ago I administered an LSF cluster and we did exactly this. We used system processing accounting. The systems I managed were running Solaris but it shouldn't be any different for Linux.

share|improve this answer

I don't know for sure but I would guess that looking at the audit subsystem to put specific audit events on the binaries you want to watch would be the best way. My hazy recollection is that the process accounting system logs a lot more than what you may want.

share|improve this answer

If your looking for a quick and free solution. Use SGE "Scheduling system".

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.