ViswaSrimaan
Cadet
Cadet
  • 771 Views

EXPECT package is not working

Jump to solution

I have installed expect package but when I type expect it is not working
rpm -qa | grep expect
expect-5.45.4-5.el8.ppc64le

expect
-bash: expect: command not found

It is throwing this error

Labels (1)
0 Kudos
1 Solution

Accepted Solutions
kpietras
Flight Engineer Flight Engineer
Flight Engineer
  • 680 Views

Re: EXPECT package is not working

Jump to solution

Sure. I think that if you have installed that package properly then something wrong with your PATH variable.
- check with 'which expect'  - in my case it is -/usr/bin/expect
-execute 'echo $PATH' and compare if it contains /usr/bin folder
   IN my case it is - /bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/ and it contains
- you can also log in/log out to reload your PATH variable if you have something defined in .bashrc

View solution in original post

0 Kudos
Reply
Loading...
3 Replies
kpietras
Flight Engineer Flight Engineer
Flight Engineer
  • 758 Views

Re: EXPECT package is not working

Jump to solution

@ViswaSrimaan 

Are you using PowerPC architecture?
Would you be able to execute uname -a and send it back here?

0 Kudos
Reply
Loading...
ViswaSrimaan
Cadet
Cadet
  • 683 Views

Re: EXPECT package is not working

Jump to solution

Sorry I couldn't share the machine details, however Yes I am using powerPC architecture.

Linux "Node_Name"  4.18.0-147.el8.ppc64le #1 SMP Thu Sep 26 15:44:34 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux

0 Kudos
Reply
Loading...
kpietras
Flight Engineer Flight Engineer
Flight Engineer
  • 681 Views

Re: EXPECT package is not working

Jump to solution

Sure. I think that if you have installed that package properly then something wrong with your PATH variable.
- check with 'which expect'  - in my case it is -/usr/bin/expect
-execute 'echo $PATH' and compare if it contains /usr/bin folder
   IN my case it is - /bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/ and it contains
- you can also log in/log out to reload your PATH variable if you have something defined in .bashrc

View solution in original post

0 Kudos
Reply
Loading...
Join the discussion
You must log in to join this conversation.