You can always patch their shell to issue
syslog calls for each command.
Is there any reason you can't use some form of process accounting instead? This is supported by most any Unix, and is generally the accepted way of recording this type of information. Using syslog seems messy, and it won't catch cases where they execute commands via other commands. What's to stop them from executing /bin/sh on their own, completely circumventing your shell?
If you go the "patch the shell" route, you'll also want to put in some logic to log only interactive sessions, else every shell script will get each line logged to syslog. There's a whole lot of things like this you'll want to be aware of. Process accounting seems like a much cleaner method.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.