https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227342
            Bug ID: 227342
           Summary: [dpv] dpv -x is broken
           Product: Base System
           Version: 11.1-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: dteske at FreeBSD.org
          Reporter: eugen at freebsd.org
                CC: stable at FreeBSD.org
An example from dpv(1) manual page does not work:
tar cf - . | dpv -x "gzip -9 > out.tgz" \
                   $( du -s . | awk '{print $1 * 1024}' ):label
In fact, even simplier command cannot work: dd if=/dev/zero bs=10000 count=1 |
dpv -x "cat >/dev/null" 10000:label
It just draws initial dialog then sits doing nothing.
The reason is that dpv(3) library uses posix_spawn_file_actions_adddup2()
function that effectively clobbers standard input file handle with a call to
dup2(terminal, 0) and ktrace(1) assures that.
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227342 --- Comment #1 from Devin Teske <dteske at FreeBSD.org> --- I will try with 11.2, but so far I was unable to replicate with either 11.0-RELEASE-p1 or 11.1-RELEASE (both amd64). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227342 --- Comment #2 from Devin Teske <dteske at FreeBSD.org> --- Tried with 11.2-RC3 and still unable to replicate -- You are receiving this mail because: You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227342
Eugene Grosbein <eugen at freebsd.org> changed:
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Closed
         Resolution|---                         |FIXED
--- Comment #3 from Eugene Grosbein <eugen at freebsd.org> ---
I could not reproduce the problem too using recent stable/11. Something got
fixed or that was some local problem. Sorry for bothering you. Closing this.
-- 
You are receiving this mail because:
You are on the CC list for the bug.