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
I use dasdls under Linux. First I saw that two lines of the dasdls output can't be redirected to a file, they always show up in the controlling terminal. Only with unbuffer(1) one gets the whole output redirected into a file. The lines are
write(2, "Hercules DASD list program Versi"...,
write(2, "(c)Copyright 1999-2015 by Roger "...,
write(0, "HHCDA004I opening mvsres.148 rea"...,
write(0, "HHCDA020I mvsres.148 cyls=560 he"...,
write(1, "mvsres.148: VOLSER=MVSRES\nZ99999"...,
So there are writes to stdout and stderr, but also two writes to stdin. The issue can be reproduced with the current HEAD (commit 59f0556) and can be traced to
I use
dasdls
under Linux. First I saw that two lines of thedasdls
output can't be redirected to a file, they always show up in the controlling terminal. Only withunbuffer(1)
one gets the whole output redirected into a file. The lines areRunning
dasdls
understrace(1)
givesSo there are writes to
stdout
andstderr
, but also two writes tostdin
. The issue can be reproduced with the current HEAD (commit 59f0556) and can be traced tologmsg (_("HHCDA004I opening...
log_write(0,bfr)
log_write(int panel,char *msg)
The logic of
log_write
finally poduces somehow awrite(0,...)
in the context ofdasdls
.The
dasdls
coming with tk4- exhibits the same issue, while thedasdls
from hercules-390/hyperion does no writes tostdin
.The text was updated successfully, but these errors were encountered: