Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1517588 - [here string] current behavior doesn't matche the behavior of ksh and zsh
Summary: [here string] current behavior doesn't matche the behavior of ksh and zsh
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: bash
Version: 7.5
Hardware: All
OS: All
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Siteshwar Vashisht
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks: 1517591
TreeView+ depends on / blocked
 
Reported: 2017-11-27 02:24 UTC by Yin.JianHong
Modified: 2017-11-27 02:27 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1517591 (view as bug list)
Environment:
Last Closed: 2017-11-27 02:25:17 UTC


Attachments (Terms of Use)

Description Yin.JianHong 2017-11-27 02:24:12 UTC
Description of problem:

according:
  https://bugzilla.redhat.com/show_bug.cgi?id=1514300
  https://bugzilla.redhat.com/show_bug.cgi?id=1514300#c7

open this bug just for remind users/customers don't use here-string like:

  read ignore fstype <<<$(df --output=fstype $mountpoint)
  #^^^ this command works on bash-4.3 and before, but doesn't on bash-4.4


Version-Release number of selected component (if applicable):
bash-4.3 and before
  #bash-4.4 has fixed this problem

How reproducible:
always

Steps to Reproduce:
0. compare:
  bash -c 'read ign fstype <<<$(df --output=fstype $mountpoint); echo $fstype'
  ksh -c 'read ign fstype <<<$(df --output=fstype $mountpoint); echo $fstype'

Actual results:
[here string] current behavior doesn't matche the behavior of ksh and zsh

Expected results:
should be same

Additional info:


Note You need to log in before you can comment on or make changes to this bug.