You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 21, 2020. It is now read-only.
We would like to see a feature where you can define a logfile for each member. With lots of members it is now quite difficult to see what is going on and what is happening on each member.
Our workaround right now is to add the HOSTNAME prefix to the output of the command like this:
ssh_task '/usr/bin/chef-client | while read i ; do [[ -n "$i" ]] && printf "%b" "[$HOSTNAME]\t$i\n"; done ; exit ${PIPESTATUS[0]}'
However, a more convenient solution would be that blender supports a seperate logfile for each member.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We would like to see a feature where you can define a logfile for each member. With lots of members it is now quite difficult to see what is going on and what is happening on each member.
Our workaround right now is to add the HOSTNAME prefix to the output of the command like this:
ssh_task '/usr/bin/chef-client | while read i ; do [[ -n "$i" ]] && printf "%b" "[$HOSTNAME]\t$i\n"; done ; exit ${PIPESTATUS[0]}'
However, a more convenient solution would be that blender supports a seperate logfile for each member.
The text was updated successfully, but these errors were encountered: