Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 6992 - /etc/profile.d/00functions.sh causes problems for ksh users
/etc/profile.d/00functions.sh causes problems for ksh users
Product: Red Hat Linux
Classification: Retired
Component: setup (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 1999-11-13 16:20 EST by David W. Tamkin
Modified: 2014-03-16 22:11 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-12-17 17:31:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David W. Tamkin 1999-11-13 16:20:01 EST
Functions definitions in /etc/profile.d/00functions.sh use this syntax:

 function name () {

Users who select /bin/ksh as their login shell (which is actually pdksh)
get an error, the function remains undefined, and later calls to that
function come up "not found," because in pdksh function definitions have
one of these two syntaxes (one to get the behavior of AT&T ksh, one to
get that specified under POSIX):

 function name {


 name() {

It's not permitted to use both the word "function" and the empty paren-

Meanwhile, /etc/profile.d/mc.sh defines a function with only the empty
parentheses, omitting the word "function," and it's fine under both bash
and pdksh.  The bash man page implies that the word "function" is totally
optional; if it were omitted in /etc/profile.d/00functions.sh, there would
be no harm under bash and much gained for ksh users.

[Hope I'm filing this report properly.]
Comment 1 Bill Nottingham 1999-11-15 11:51:59 EST
I can't find an /etc/profile.d/00functions.sh anywhere in our
distribution. What does rpm -qf /etc/profile.d/00functions.sh say?

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