hrmm that's not what I was seeing. Even though the `sudo` cmd is backgrounded, it still maintains a handle to our shell session as its stdout, so even though `sleep` is executing in the foreground, we will still receive output from both. Sudo fails almost immediately, so `sleep 5` should cover it. During my testing last night i hit that check a lot of times. Why can't we keep the `sleep 5`? It adds a slight delay to the module but both sessions end up staying alive