Creating the log file directory

[tdelov]

sudosh fails if the directory is not present.

[kovacs-andras]

I can confirm that. And there are many other ways how it can fail like:

• permission changes on any parent or the sudosh directory
• when the /var/log volume is full (no free space or inode) and sudosh2 can't create new log files
• etc.

This is an easy tool. It won't give you an extra layer of security but you will have a directory what anyone can fill up with anything. I have a single line in my bashrc which removes the sudosh logs instantly when I'm logging in to a server.

I recommend to check this project instead: https://github.com/Scribery/tlog
Or log sessions with sudo (sudo can log remotely too now)

If you only need to log your sessions than this video can be interesting for you: https://youtu.be/DYHadkG9iFg

[Chewbakka-Wakka]

when the /var/log volume is full (no free space or inode) and sudosh2 can't create new log files - this can happen easily also given how much data can be logged, grows massively depending on user counts and length of sessions.