individual config file

[Brian K. White]

On 12/15/2011 11:12 AM, Craig Tooker wrote:
> On 12/15/2011 10:59, Robert T. Repko (R Squared Consultants) wrote:
>> Believe it or not at 12/15/2011 10:47 AM, Kenneth Brody said:
>>> On 12/15/2011 10:00 AM, Robert T. Repko (R Squared Consultants) wrote:
>>>> Running filePro 5.6 on SCO Unix 5.0.7 Korn shell.
>>>> I need to setup individual config files for certain users.  I set the
>>>> environment variable PFCONFIG in the users .profile but when I log in
>>>> as the user the environment variable doesn't appear and the personal
>>>> config file doesn't show.  If I set the variable from the command
>>>> prompt it appears and the personal config file shows.
>>>>
>>>> Entry in .profile
>>>> PFCONFIG=/u/appl/fp/lib/config.sam
>>>> export PFCONFIG
>>>>
>>>> What am I missing?
>>> What shell are they using?  As I recall, some shells use a file
>>> other than "~/.profile".  For example, I believe the C shell uses "~/.cshrc".
>>>
>>> --
>>> Kenneth Brody
>> korn shell
>> I made the same entries in .kshrc but it didn't work.
>> PFCONFIG=/u/appl/fp/lib/config.sam;export PFCONFIG
> You've checked the /etc/passwd file to make sure they are using /bin/ksh
> or on your system /bin/sh is a link to /bin/ksh ?  Most Linux
> distributions default /bin/sh as a link to /bin/bash.
>
> Are the lines in this email a cut and paste from the lines in the config
> file?
>
> Craig

On SCO OSR5 /bin/sh and /bin/ksh will both read ~/.profile and neither 
is a link to bash or anything else. /bin/sh is an old bourne shell, 
stock /bin/ksh is ksh88. ksh93 is available in an add-on but it does not 
overwrite /bin/ksh. (ksh93 will read ~/.profile too)
Bash is available in an add-on too, but unlike in most linux distros, 
the bash install does not include fake sh or ksh links.

On 5.0.6 and 5.0.7 in particular, ~ is in /u by default, which is 
different from where it was in older versions, /usr,
and may be changed in /etc/default/accounts to something more sensible 
like /home.
Lots of opportunities for things to not be where you expect them and few 
assumptions are safe.

.kshrc is the wrong place for this, but never the less it should have 
worked, so it's interesting that it didn't. That hints at wrong 
directory or wrong ownerships or permissions.

Please show the following:

grep "^username:" /etc/passwd

ls -l /u/username

ls -lR /u/username

cat /u/username/.profile

-- 
bkw