tlog
snoopy
tlog | snoopy | |
---|---|---|
4 | 3 | |
296 | 1,171 | |
1.7% | 0.4% | |
5.2 | 5.9 | |
3 months ago | 7 months ago | |
C | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tlog
-
Help with installing tlog on Debian 10
https://salsa.debian.org/ascii/tlog/-/tree/debian/latest https://github.com/Scribery/tlog
- How to log bash commands in some simple way?
- Tlog: Terminal I/O Logger
-
Bash-Oneliner: A collection of handy Bash One-Liners and terminal tricks
Enterprises that requires logging of user actions will very likely not being doing it at the shell level, either through compiled in options, or shell history.
Instead, the Kernel has built in functionality called Auditd[0], which is capable of logging any and all executions, file or socket accesses, and much more. Along with included tooling for quickly finding and alerting on events[3].
Further, if terminal logging or playback is really required (usually not), it's generally done through pam with tlog[1]. Red Hat 8 and above come with built-in tlog support[2].
[0] https://access.redhat.com/documentation/en-us/red_hat_enterp...
[1] https://github.com/Scribery/tlog/blob/main/README.md
[2] https://access.redhat.com/documentation/en-us/red_hat_enterp...
[3] https://wiki.archlinux.org/title/Audit_framework
snoopy
-
How to Capture Bash History?
If you're looking for a command auditing solution, it looks like some people have rigged up /etc/profile to send every command to syslog directly, some people use software like snoopy, etc. - those are all bypassable by a user, though. Using the kernel's audit functionality to snoop execve (setup auditd, set up rules like "auditctl -a exit,always -S execve") has plenty of downsides, but would be a real auditing solution.
- How to log bash commands in some simple way?
-
How do you find where the rsync process is coming from?
Have a look at auditd: it can log system calls like execve. Or snoopy. Or use the answers from here.
What are some alternatives?
trice - 🟢 super fast 🚀 and tiny 🐥 embedded device 𝘾 printf-like trace ✍ code, works also inside ⚡ interrupts ⚡ and real-time PC 💻 logging (trace ID visualization 👀)
bfs - A breadth-first version of the UNIX find command
fgprof - 🚀 fgprof is a sampling Go profiler that allows you to analyze On-CPU as well as Off-CPU (e.g. I/O) time together.
Gearboy - Game Boy / Gameboy Color emulator for macOS, Windows, Linux, BSD and RetroArch.
bash-preexec - ⚡ preexec and precmd functions for Bash just like Zsh.
cassette_deck - 🖭 CLI gif recorder, simplified
jdupes - A powerful duplicate file finder and an enhanced fork of 'fdupes'.
vscode-bash-debug - Bash shell debugger extension for VSCode (based on bashdb)
i3lock-color - The world's most popular non-default computer lockscreen.
logswan - Fast Web log analyzer using probabilistic data structures
audit-userspace - Linux audit userspace repository