On 10/6/14, 4:04 AM, Tajthy, Tamas wrote:
> Hi,
>
> I have a minor issue with the newest bash-3.2-33.el5_11.4 (RedHat) package.
> Same happens on Debian Wheezy (unfortunately I do not know that version
> number now).
>
> I usually define in my .bash_profile some functions called "..", "...",
> "...." and so on. After the latest package was installed I continuously get
> error messages shown above when I start a (sub-)bash from the login bash:
>
> bash: error importing function definition for `BASH_FUNC_..'
> bash: error importing function definition for `BASH_FUNC_...'
> bash: error importing function definition for `BASH_FUNC_....'
>
> etc... And these functions cannot be used in the child bash. But no problem
> is shown when bash is a login shell (called as "bash -l") and the definition
> is read from the .bash_profile.
You should open a bug report with Red Hat and Debian. They used a stricter
version of the patches that result in bash refusing to import shell
functions whose names are not valid shell identifiers. The official
patches I released, while imposing this requirement early (bash32-052),
allow names that are not valid identifiers when the shell is not running
in Posix mode (as of bash32-054).
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
