ramfree17 Posted October 14, 2003 Report Share Posted October 14, 2003 yes, your response are very adequate. see what/bin/bash tells you. It should just open another instance of the command interpreter! let me add a request to this one. try to see if bash will return its version. bash -v or bash --version (sorry im not in a linux machine atm). if everything fails, post the output of the command $ export . you might have to pipe it to a file though if its too long (i.e. $export > somefile). ciao! Quote Link to comment Share on other sites More sharing options...
paCkeTroUTer Posted October 14, 2003 Author Report Share Posted October 14, 2003 I maybe doing something wrong here. I tried the following: [jeffery@localhost jeffery]$ /bin/bash [jeffery@localhost jeffery]$ as you can see nothing happens when I give that command :? Please correct me if I have given the command the wrong way. Thanks let me add a request to this one. try to see if bash will return its version. bash -v or bash --version (sorry im not in a linux machine atm). if everything fails, post the output of the command [jeffery@localhost jeffery]$ bash -version GNU bash, version 2.05b.0(1)-release (i586-mandrake-linux-gnu) Copyright (C) 2002 Free Software Foundation, Inc. [jeffery@localhost jeffery]$ Quote Link to comment Share on other sites More sharing options...
paCkeTroUTer Posted October 14, 2003 Author Report Share Posted October 14, 2003 if everything fails, post the output of the command $ export . you might have to pipe it to a file though if its too long (i.e. $export > somefile). ciao! declare -x DISPLAY=":0" declare -x GDK_USE_XFT="1" declare -x G_BROKEN_FILENAMES="1" declare -x HISTCONTROL="ignoredups" declare -x HISTSIZE="1000" declare -x HOME="/home/jeffery" declare -x HOSTNAME="localhost" declare -x INPUTRC="/etc/inputrc" declare -x LANG="en_AU" declare -x LANGUAGE="en_AU:en_GB:en" declare -x LC_ADDRESS="en_AU" declare -x LC_COLLATE="en_AU" declare -x LC_CTYPE="en_AU" declare -x LC_IDENTIFICATION="en_AU" declare -x LC_MEASUREMENT="en_AU" declare -x LC_MESSAGES="en_AU" declare -x LC_MONETARY="en_AU" declare -x LC_NAME="en_AU" declare -x LC_NUMERIC="en_AU" declare -x LC_PAPER="en_AU" declare -x LC_TELEPHONE="en_AU" declare -x LC_TIME="en_AU" declare -x LESS="-MM" declare -x LESSKEY="/etc/.less" declare -x LESSOPEN="|/usr/bin/lesspipe.sh %s" declare -x LOGNAME="jeffery" declare -x LS_COLORS="no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01; 35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=01; 32:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.tar=01; 31:*.tgz=01;31:*.tbz2=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01; 31:*.lha=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01; 31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01; 35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*.tif=01;35:*.tiff=01;35:" declare -x MAIL="/var/spool/mail/jeffery" declare -x NLSPATH="/usr/share/locale/%l/%N" declare -x OLDPWD declare -x PATH="/bin:/usr/bin:/usr/local/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/home/jeffery/bin" declare -x PS1="[u@h W]$ " declare -x PWD="/home/jeffery" declare -x QT_XFT="0" declare -x SECURE_LEVEL="4" declare -x SHELL="/bin/bash" declare -x SHLVL="2" declare -x SSH_ASKPASS="/usr/lib/ssh/gnome-ssh-askpass" declare -x TERM="xterm" declare -x TMP="/home/jeffery/tmp" declare -x TMPDIR="/home/jeffery/tmp" declare -x USER="jeffery" declare -x XAUTHORITY="/home/jeffery/.xauthwRuhw1" declare -x ftp_proxy declare -x http_proxy="http://proxy.iprimus.com.au" Quote Link to comment Share on other sites More sharing options...
Qchem Posted October 14, 2003 Report Share Posted October 14, 2003 >as you can see nothing happens when I give that command Don't worry, thats what should happen, if you type exit after that you'll return to your original instance of bash. Quote Link to comment Share on other sites More sharing options...
Gowator Posted October 14, 2003 Report Share Posted October 14, 2003 bash -v should return your version and su - jeffery should open a complete new login instance if anything is being set incorrectly it'll show up same for the export > myexports.txt We all seem to be looking for the same stuff here so just keep the output coming!!! also try a ls -a .ba* in your /home/jeffery this should list the bash login files :D Quote Link to comment Share on other sites More sharing options...
paCkeTroUTer Posted October 14, 2003 Author Report Share Posted October 14, 2003 bash -v should return your version It spits out lots of info so I have put it into a file and onto my server. Click here and su - jeffery should open a complete new login instance if anything is being set incorrectly it'll show up It does exactly what you have described when I type the above command. It brings in a password prompt and makes me login to the shell. also try a ls -a .ba* in your /home/jeffery this should list the bash login files :D here is the result: [jeffery@localhost jeffery]$ ls -a .ba* .bash_history .bash_logout .bash_profile .bashrc [jeffery@localhost jeffery]$ Quote Link to comment Share on other sites More sharing options...
Gowator Posted October 14, 2003 Report Share Posted October 14, 2003 bash -v Shouldn't do that. it should just print out the version info BUT it is taking everything literally. I (we) probably need to look through it ... OR You might try to urpmi bash that definately shouldn't happen though! Also Make yourself another user (you can use the MCC) (maybe) see what bash -v does from the other user! Try and run the sample.sh etc!!!!! This will let you know if its JUST that user (which i suspect) or ALL. i.e. presently it seems root is the exception, but root might be reacting normally anbd your USER isn't! Quote Link to comment Share on other sites More sharing options...
Qchem Posted October 14, 2003 Report Share Posted October 14, 2003 bash -v does print out all of your bash variables - it's the same as bash --verbose. bash --version prints the version information. Quote Link to comment Share on other sites More sharing options...
paCkeTroUTer Posted October 14, 2003 Author Report Share Posted October 14, 2003 bash -v does print out all of your bash variables - it's the same as bash --verbose. bash --version prints the version information. Thats what I thought too... except I didn't know what the v stood for. I have done the bash -version command at the very top of page 2 of this thread. Do you still want me to add a new user and see if everything is fine with the new user ? Quote Link to comment Share on other sites More sharing options...
Gowator Posted October 14, 2003 Report Share Posted October 14, 2003 Well it won't take long - New user that is and it should at least provide a clue. Its good to have a spare on anyway to test things on :D + We can use the bash -v i.e. if the new user CAN run bash AND your user can't THEN we can diff the two outouts and find whats different!!! Quote Link to comment Share on other sites More sharing options...
paCkeTroUTer Posted October 14, 2003 Author Report Share Posted October 14, 2003 ok here you go.. the old user and new user bash -v Old User New User and I was able to get positive results of both the sample scripts: [sotheara@localhost sotheara]$ ./sample.sh If you see this then you can execute bourne shell scripts. [sotheara@localhost sotheara]$ ./sample2.sh If you see this then you can execute bourne shell scripts. [sotheara@localhost sotheara]$ Quote Link to comment Share on other sites More sharing options...
ramfree17 Posted October 14, 2003 Report Share Posted October 14, 2003 if i were you then i would take the cowardly way out and just recreate the user. :#: but if you want to troubleshoot this then its good experience. ;) ciao! Quote Link to comment Share on other sites More sharing options...
Gowator Posted October 14, 2003 Report Share Posted October 14, 2003 Like RamFree says Theirs an easy way and a hard way. If you have lots of stuff in the directories like your .kde etc. then you might wanna copy these to the new user, one by one. One thing you can do, and its a bit of a shot is use diff on the bash -v >jeffery.txt and bash -v > newuser.txt When su - <user> appropraitely. ie. from jeffery diff jeffery.txt ../<newuser>/newuser.txt This will pick out any differences in the two files. You can then take this difference and find where its being set. grep <atextstring> .bash* Or find . | grep ''<atextstring> " Which from /home/jeffery should recursively test each file You can probably spped it up with use of the arguaments to find, i.e. only executable files Quote Link to comment Share on other sites More sharing options...
sarah31 Posted October 14, 2003 Report Share Posted October 14, 2003 you should not be able to install anything to the system as strict user. trying to enable this is very dangerous and you risk compromising your system. *nixes are designed to separate administrating duties from global user to one root user. this ensures that only the person who know the system will not fork it up. there are near root but not full root modes a user can assume to make administering single user systems faster. these are su (superuser) or sudo. both allow a large amount of root permissions to the user while still protecting against "dangerous" actions. never compromise your system to the point where you have user and root able to do install software system-wide. if you do that you may as well use windows. or pre OS X Mac OSes. Quote Link to comment Share on other sites More sharing options...
Gowator Posted October 14, 2003 Report Share Posted October 14, 2003 they aren't trying to do that, well maybe... But they do have a genuine problem with bash. They can't run any script in bash as their main user. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.