Bug 3602 - zsh startup occasionally prints nonfatal error message.
zsh startup occasionally prints nonfatal error message.
Status: CLOSED NEXTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: zsh (Show other bugs)
6.0
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-06-20 16:51 EDT by George Karabin
Modified: 2015-01-07 18:37 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-09-24 23:36:09 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 George Karabin 1999-06-20 16:51:24 EDT
I use zsh as my user account's default shell. On two
different RH 6.0 clean installations, I *sometimes* see this
error message when starting a gnome terminal:

/etc/zshenv: parse error: condition expected: -eq [12]

I can't remember ever seeing the problem when starting a new
zsh from the command line. ('zsh' or 'exec zsh'). A cheezy
20-try test shows that the problem doesn't happen when
invoking a new zsh from the command line.

I'm not certain what bad effects, if any, this is likely to
have. The only thing that I can think of is that, perhaps, a
root user running a gnome terminal with a shell of zsh would
not get a path that includes /sbin and /usr/sbin, from time
to time.
Comment 1 Michael K. Johnson 1999-09-24 23:36:59 EDT
Probably fixed for our upcoming Red Hat Linux 6.1 release.  Re-open
this bug if after upgrading to zsh-3.0.5-15 or later you still have
this problem.  (3.0.5-15 will show up in the next RawHide release).

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