4 ms·
I used supervisord for anything complex, which is where I think systemd get's it's syntax from. Anisble abstracts some stuff (ensure running, running as use, e
by KaiserPro 8y ago
I used supervisord for anything complex, which is where I think systemd get's it's syntax from.
Anisble abstracts some stuff (ensure running, running as use, etc) but for more complex stuff (process type, dependency management etc) you're on your own shipping system files.
My main beef is actually three things:
1) crap error messages,
2) crap validataion
3) journalctl being a crap VIM wrapper.
of all of them, journalctl is the most obnoxious. Instead of deffering to the system viewer it enforces their crap viewer. It truncates by default, and without restarting the viewer, or forcing it through less. (Why didn't they use less by default? less code to maintain..)
- zaarn 8y agoJournalctl uses less as a pager by default, you can set the env variable SYSTEMD_PAGER to specifiy what pager to use (or just PAGER) and SYSTEMD_LESS to specify parameters to pass to less. journalctl has no own pager implementation and if no pager is installed then none is used. I give you validation and error messages, systemd is a bit sparse on that front. Would be easier if there was a way for programs and services to signal back error messages to report. edit: You can actually enforce non-wrapping by setting SYSTEMD_LESS to FRXMK (the S option that is otherwise included causes truncating, if omitted you get wrapping) This can all be configured in /etc/profile, .bashrc and friends