For some reason my path has a problem. I did not change anything that would affect all users PATHs so I believe it started after a yum upgrade.

Using default /etc/profile and /etc/bashrc I get the following errors on login:

sh: grep: command not found
sh: gzip: command not found
Bad Character Height 0

Very strange. I added a couple pathmunge calls to add usr/bin and bin to my path but it seems these are executed late in the login process, they have no effect until after the user is logged in. Then life appears as usual.

Now I am fairly new to Fedora. I came from Slackware where the problem would be easy to spot and solve but this script nonsense in Fedora is garbage. The login process seems over complicated.

Can someone point me in the direction to solve my problem? In which order are scripts executed in a login sequence? All processes that start on boot start properly and this problem happens for all users including root. Is there an RPM I can reinstall that will reset all these configs to their default in case one of them somehow got modified?

Thanks in advance

do you always post your question on fedora's forum and here?
http://forums.fedoraforum.org/showth...057#post985057

Wow, how incredibly helpful. You should be proud after a find like that.

Your home directory has a few hidden files related logins and accounts, like .bash_history .bash_logout .bash_profile .bashrc and I would start out checking if their contents have been changed or contain unusual settings. The /etc based files are only used when these files are not present or when new home directories and users are created (maybe one problem is copied with each new user).

I'm using Fedora since release 1 on a whole bunch of PC's but your problem appears to be quite unusual and unique. I wouldn't agree to call this a typical Fedora problem or even saying that upgrading did something. I was able to upgrade a Fedora 1 system up to Fedora 8 using 'yum upgrade' without such mysteries.

And by the way, use .bash_profile to set your PATH in a persistant way.

Error messages like
are extremely uncommon, I've never run into these. Are grep and gzip otherwise functional?

Unfortunately I'm not much of a help on this topic, but in all honesty you didn't provide a lot of information to start out with.

The best I can say is that your problem is very unique, though this probably will not make you happy.

Regards,
SIMP

Fedora User