-
This flexibility may prove useful, I'm looking foward to it. I was curious if you plan on adding a 66 command that shows part of the logs for all services in relevant trees, sort of like how journalctl does? For example if I want output of last 4 lines to all files in /var/log/66/service/current
-
💬 @ObarunAuthor OwnerFor example if I want output of last 4 lines to all files in /var/log/66/service/current
For now you can do
svs=( $(66 tree status -no contents global) ); for sv in ${svs[@]}; do 66 -z status -o name,logfile -p4 ${sv};doneor for a script destination
svs=( $(66 tree status -no contents global) ); for sv in ${svs[@]}; do 66 status -no logfile -p4 ${sv};donefor the whole user (root or not)
svs=( $(66 tree status -no contents) ); for sv in ${svs[@]}; do 66 status -o logfile -p4 ${sv};doneHowever, i agree with the facts that wrapper are missing mostly regarding script application. Some wrapper like isrunning, isenabled, and so on. So yes, at some points some facilities will be added like this one
Edited by Eric Vidal
Please register or sign in to comment