• 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

  • Author Owner

    For 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};done

    or for a script destination

    svs=( $(66 tree status -no contents global) ); for sv in ${svs[@]}; do 66 status -no logfile -p4 ${sv};done

    for the whole user (root or not)

    svs=( $(66 tree status -no contents) ); for sv in ${svs[@]}; do 66 status -o logfile -p4 ${sv};done

    However, 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
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment