-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Screen/tmux is not needed #13
Comments
Interesting, I will try that later. That could get rid of server_do(). The jank that is server_read() would live on albeit scraping journalctl instead of tmux. I wonder if journalctl can automatically parse the join/leave messages and push to the IRC bot and any future web hooks I've considered adding (likely just a line of wget). That would make the jank that is MCBElog.sh unneeded with up to 1 minute less delay as it would read on push instead of scraping once a minute. Only possible downside is while tmux confuses people having to use journalctl to see the output of a command echo'd to the pipe is also going to confuse some users. Edit: I'm definitely putting the instance name in the description later. That was an oversight of mine, thank you. |
I addressed the description lacking instance name, I'll play with a separate branch trying systemd sockets later this weekend. Gotta apply for classes, read backup logs, and other stuff first. |
Branch werm_socket has some progress on scraping logs the same way I use |
I'm having a lot of trouble getting input logged the way tmux did. I just want standard in to be logged in the journal but I haven't found anything in systemd or Bash for that. |
Latest 2 commits fix this issue. My services and scripts now use systemd sockets and journalctl. I may readd tmux compatibility later but that is irrelevant to this issue, the services will continue to use systemd sockets. |
Wow that was fast, sorry I had bunch of github notifications to read through. This is cool.
This is not really necessary, it only pollutes such a nice and clean (tmux-free) config file now :-) I am planning an article for opensource.com about SELinux policy and this repo will be totally featured as the recommended way! Kudos. |
Hey, stumbled upon your scripts. Nice, however tmux is not needed at all, systemd can create FIFO for STDIN:
This is much more secure, I am working on implementing SELinux policy on top of that. With tmux that is not possible. FYI if you want to simplify your scripts a bit.
The text was updated successfully, but these errors were encountered: