The UNIX and Linux Forums  

Go Back   The UNIX and Linux Forums > Top Forums > UNIX for Advanced & Expert Users
Google UNIX.COM


UNIX for Advanced & Expert Users Advanced UNIX and Linux questions go here. Expert-to-Expert.

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
expect and stty paths are different and resulting in error. The Nemi UNIX for Dummies Questions & Answers 6 07-17-2008 08:50 AM
Exiting from script when error occurs Sreejith_VK Shell Programming and Scripting 4 04-25-2008 12:53 AM
error occurs while some users login rrlog HP-UX 0 08-12-2007 01:55 PM
Error when installing GCC chrisanto_2000 SUN Solaris 1 06-21-2007 03:00 AM
error while installing gcc sveera SUN Solaris 1 06-21-2005 10:05 AM

Reply
 
Submit Tools LinkBack Thread Tools Search this Thread Display Modes
  #1  
Old 09-11-2008
Registered User
 

Join Date: Jul 2007
Posts: 91
stty: error occurs when installing rpm

Hello All,

when I install rpm

rpm --install rpm packagename

I got the following errors

stty:standard input:invalid argument
stty:standard input:invalid argument

I dont know what i have to do exactly.
I search on google for the same but not a particular standard solution is given

please help me to overcome this problem

Regards,
Amit
Reply With Quote
Forum Sponsor
  #2  
Old 09-11-2008
 

Join Date: May 2008
Location: Sydney, Australia
Posts: 920
Usually this is because some user (maybe root) has some stty commands in their .profile or .bash_profile or .bashrc, usually something like stty erase ^H.

You can safely ignore those messages, however if you like to be tidy you can prevent them from coming up by changing them as follows:

Code:
# only use stty if stdin is a terminal
[[ -t 0 ]] && stty erase ^H
It is a good idea to do this as well if you have some software that analyses the output of some commands and does not expect these "stty:standard input:invalid argument" messages.
Reply With Quote
  #3  
Old 09-11-2008
Registered User
 

Join Date: Jul 2007
Posts: 91
Quote:
Originally Posted by Annihilannic View Post
Usually this is because some user (maybe root) has some stty commands in their .profile or .bash_profile or .bashrc, usually something like stty erase ^H.

You can safely ignore those messages, however if you like to be tidy you can prevent them from coming up by changing them as follows:

Code:
# only use stty if stdin is a terminal
[[ -t 0 ]] && stty erase ^H
It is a good idea to do this as well if you have some software that analyses the output of some commands and does not expect these "stty:standard input:invalid argument" messages.
Helo thx for yr reply

I have changed
cd /home/sroot
.bashrc
.bash_profile
cd /etc

profile
bashrc

but still got the same error

Regards,
Amit
Reply With Quote
  #4  
Old 09-11-2008
 

Join Date: May 2008
Location: Sydney, Australia
Posts: 920
What RPM are you installing? Maybe it executes its install scripts under another user ID.
Reply With Quote
  #5  
Old 09-11-2008
Registered User
 

Join Date: Jul 2007
Posts: 91
Quote:
Originally Posted by Annihilannic View Post
What RPM are you installing? Maybe it executes its install scripts under another user ID.
Helo thx for replying me.

I m installing my own build RPM .

I m making rpm on my build machine.

after that I install it from my installer script using root user

Regards,
Amit
Reply With Quote
  #6  
Old 09-11-2008
 

Join Date: May 2008
Location: Sydney, Australia
Posts: 920
What do you have in the %pre and %post sections of your spec file?
Reply With Quote
  #7  
Old 09-14-2008
Registered User
 

Join Date: Jul 2007
Posts: 91
Quote:
Originally Posted by Annihilannic View Post
What do you have in the %pre and %post sections of your spec file?
Helo thx for replying me.

I have following in the %pre

%prep
echo 'Prep' $RPM_BUILD_ROOT
%setup -q
%{__cat} <<EOF >%{_tmppath}/find_requires
#! /bin/sh
exec %{__find_requires} | /bin/egrep -v 'libclntsh.so.10.1' | /bin/egrep -v 'libnnz10.so'
exit 0
EOF
chmod +x %{_tmppath}/find_requires
%define _use_internal_dependency_generator 0
%define __find_requires %{_tmppath}/find_requires

%build
echo 'Build' $RPM_BUILD_ROOT
[ ${RPM_BUILD_ROOT} != "/" ] && rm -rf $RPM_BUILD_ROOT
mkdir -p $RPM_BUILD_ROOT

I have following in the %post


%post
export SW_SOFTWARE_SPEC="%{name},COMPONENT,r=%{version}"
export FILESET="COMPONENT"
export PRODUCT="%{name}"
%{pdsdir}/shell/COMPONENT/postinstall && %{pdsdir}/shell/COMPONENT/configure


Regards,
Amit
Reply With Quote
Google The UNIX and Linux Forums
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes




All times are GMT -7. The time now is 01:21 PM.


Powered by: vBulletin, Copyright ©2000 - 2006, Jelsoft Enterprises Limited.
The UNIX and Linux Forums Content Copyright ©1993-2008. All Rights Reserved.Ad Management by RedTyger Visit The Complex Event Processing Blog

Content Relevant URLs by vBSEO 3.2.0