This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 3200 - shell read command does not behave as expected
shell read command does not behave as expected
Status: CLOSED DUPLICATE of bug 8894
Product: Red Hat Linux
Classification: Retired
Component: pdksh (Show other bugs)
5.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-06-01 17:08 EDT by ron.kyles
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-05-29 14:00:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description ron.kyles 1999-06-01 17:08:11 EDT
The following script returns nulls in the read command
arguments; however if you comment out the read command, awk
will print the field variables:

#!/bin/ksh

IFS=' '

    echo "1;/usr/tistar/bin/flpnm.asc;Name;Ascending;lp_" |
\
    awk -F\; '{if(NR == tc) {printf("%s %s %s %s\n", $2, $3,
$4, $5)}}' tc=1 | \
    read file field sortorder value
    echo $file $field $sortorder $value
Comment 1 Jeff Johnson 1999-07-23 05:11:59 EDT
This is still a problem in pdksh-5.2.14-1.
Comment 2 Jeff Johnson 1999-09-02 14:09:59 EDT
The fix won't be in Red Hat 6.1. I'm preserving the bug by changing
the state to REMIND.
Comment 3 Trond Eivind Glomsrxd 2001-05-29 14:01:05 EDT

*** This bug has been marked as a duplicate of 8894 ***

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