Bash throwing “ignored null byte in input” warning in a script

bash

I have a script that runs in bash 4.3 and checks for an rpm package.
I want the same script to run successfully on bash 4.4 but the script throws a warning “warning: command substitution: ignored null byte in input”.
Below is the line that is throwing this warning:

FIND_RPM=find /opt/RPM/components -type d -name enum-1.1.6 -print0

The script is executed in debug mode as below:

 +++ find /opt/RPM/components -type d -name eum-1.1.6 -print0
bash: warning: command substitution: ignored null byte in input
++ LINSEE_RPM=/opt/RPM/components/enum-1.1.6

How should i now rewrite this line to ignore this warning and silently drop this null byte as is done in bash4.3?

Best Answer

As you are not using the \0 bytes that the option -print0 generates, you might want:

 FIND_RPM="$(find /opt/RPM/components -type d -name enum-1.1.6 -print)"

Related Solutions

Bash completion throwing syntax error

Bash completion is modular; different packages provide their own completion extensions. Another package probably contains the bug. Try mv /etc/bash_completion.d{,.old} and see if that fixes it. If so, do mv /etc/bash_completion.d{.old,} to move it back again, and then move individual files out of the /etc/bash_completion.d directory one by one to identify the file that is causing the problem. (The directory might be called something slightly different on Peppermint.)

Bash – Using bash variable with escape character in awk to extract lines from file

Several options here:

pat1, pat2 treated as regexps:
```
pat1="A sentence here"
pat2='\*{58}'
export pat1 pat2
awk '$0 ~ ENVIRON["pat1"], $0 ~ ENVIRON["pat2"]'
```
Note that mawk and versions of gawk prior to 4.0.0 do not support the {} extended regular expression operator. For old versions of gawk, you can pass the POSIXLY_CORRECT environment variable to make it recognise it.

Here using the start-condition, end-condition [{action}] approach, but you could do the same with your p flag approach.
pat1, pat2 treated as fixed strings:
```
pat1="A sentence here"
pat2=$(printf '*%.0s' {1..58})
export pat1 pat2
awk 'index($0, ENVIRON["pat1"]), index($0, ENVIRON["pat2"])'
```
Here, index() searches for the needle (the variable content) anywhere in the haystack (the current record (line)), but you could also do a simple full-line comparison:
```
awk '"" $0 == ENVIRON["pat1"], "" $0 == ENVIRON["pat2"]'
```
(the "" is to force a string comparison even in cases where both $0 and ENVIRON["patx"] are numerical).

Avoid using -v to pass data that may contain backslash characters as awk does some C escape sequence (\n, \b, \\...) processing on them so you'd need to escape the backslashes (and with GNU awk 4.2 or above, values that start with @/ and end in / are also a problem). Same goes for variables passed like awk '...code...' awkvar="$shellvar". Use ENVIRON or ARGV instead.

See this answer to a related question for further details.

Best Answer

Related Solutions

Bash completion throwing syntax error

Bash – Using bash variable with escape character in awk to extract lines from file

Related Question