[ovirt-users] Re: Bug in the engine-backup script when no attached TTY -- Easy fix

2023-01-17 Thread Yedidyah Bar David
On Wed, Jan 18, 2023 at 9:09 AM wrote: > > That is very useful. You are right; I was assuming a non-attached TTY; > however, it could very well be a closed/re-directed stdout. The NetBackup > client does fun things with stdout/stderr for logging and data transfer. I > will run some tests

[ovirt-users] Re: Bug in the engine-backup script when no attached TTY -- Easy fix

2023-01-17 Thread eshwayri
That is very useful. You are right; I was assuming a non-attached TTY; however, it could very well be a closed/re-directed stdout. The NetBackup client does fun things with stdout/stderr for logging and data transfer. I will run some tests tomorrow to check. The scenario is quite simple.

[ovirt-users] Re: Bug in the engine-backup script when no attached TTY -- Easy fix

2023-01-17 Thread Yedidyah Bar David
On Tue, Jan 17, 2023 at 11:37 PM wrote: > > The output() function. This line: > > printf "%s\n" "${m}" > > It will fail if there is no attached TTY, Are you sure it requires an attached _TTY_? Not merely stdout? It indeed requires a TTY in certain cases (see readdbpassword) but not in the