Red Hat

Originally Posted by Pradeep Jangra

Thanks for the commands but I had tried all these options (obviously in home directory) but there is no sign of .profile or .login files. These are the only files coming as result of ls -d .* ->
. .. .bash_history .sh_history .snapshot

I have been thinking about creating new profile file but I'm scared if it overwrote any of the existing paths so don't want to take chances.
On top of it, still confused why these files are not available and how the shell is working properly. Is there something which I am not aware of..!

Originally Posted by MadeInGermany

ksh does not use a .kshrc file, but the environment variable ENV.
Create a .kshrc file with a 1st line

Code:

echo hello .kshrc

and put the following in the .profile:

Code:

#ksh reads this startup file:
ENV=$HOME/.kshrc; export ENV

You will find that each interactive ksh reads the .kshrc first; a ksh login shell reads .kshrc after .profile.

If the shell is invoked by exec(2), and the first character of argument zero ($0) is -, then the shell is assumed to be a login shell and commands are read from /etc/profile and then from either .profile in the current directory or $HOME/.profile, if either file exists. Next, for interactive shells, commands are read from the file named by performing parameter expansion, command substitution, and arithmetic substitution on the value of the environment variable ENV if the file exists. If the -s option is not present and arg and a file by the name of arg exists, then it reads and executes this script. Otherwise, if the first arg does not contain a /, a path search is performed on the first arg to determine the name of the script to execute. The script arg must have execute permission and any setuid and setgid settings will be ignored. If the script is not found on the path, arg is processed as if it named a built-in command or function.