Re: Exiting an unconditional juju debug-hooks session

2017-06-05 Thread Dmitrii Shcherbakov
John, Any will work: - ./hooks/$JUJU_HOOK_NAME && tmux kill-session -t $JUJU_UNIT_NAME - ./hooks/$JUJU_HOOK_NAME, C-a d - C-a 0, exit, ./hooks/$JUJU_HOOK_NAME, C-a exit This is because we have an `exec` on new session creation https://github.com/juju/juju/blob/develop/worker/uniter/runner/debug/

Re: Exiting an unconditional juju debug-hooks session

2017-06-04 Thread John Meinel
Doesn't the equivalent of ^A ^D (from screen) also work to just disconnect all sessions? (http://www.dayid.org/comp/tm.html says it would be ^B d). Or switching to session 0 and exiting that one first? I thought we had a quick way to disconnect, but its possible you have to exit 2x and that fast f

Exiting an unconditional juju debug-hooks session

2017-06-04 Thread Dmitrii Shcherbakov
Hi everybody, Currently if you do juju debug-hooks # no event (hook) in particular each time there is a new event you will get a new tmux window open and this will be done serially as there is no parallelism in hook execution on a given logical machine. This is all good and intentional but when