[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-user
Subject:    Re: HELP! KFM in super user mode
From:       "Bruce J. Carter" <bjcarter () gte ! net>
Date:       1998-06-30 1:57:52
[Download RAW message or body]

Hi Ivo,


On 29-Jun-98 Ivo Naninck wrote:
> 
> Bruce,
> 

[copious gratuitous deletions]

> 
> First I put it in kfmsu2, the one which actually does the trick. Well,
> is
> supposed to do the trick :-(
> Then, with the line still in kfmsu2 I did put it in the kfmsu,
> which, in it turn, runs the kfmsu2.
> 
> Changing the shell in /etc/passwd to /bin/sh would NOT help, I think,
> because:
># ls -l /bin/sh
> lrwxrwxrwx   1 root     root            4 Oct  6  1996 /bin/sh -> bash
># 
> 

There is no difference between the two. th #!/bin/sh is a historical
convention, and bash answers to either on and regular bourne shell scripts
will work with bash. BUt you answered your own problem without even
knowing it see below...

> Besides that:
> 
> /home/inaninck> sh
> sh-2.00$ FOO=rubbish; export FOO
> sh-2.00$ env | grep FOO
> FOO=rubbish
> sh-2.00$ 
> 

This correct, and is what one would expect.

> It seems to work in bash, as /bin/sh is a link to /bin/bash
> And my default shell is bash, so what would actually do the line
>#!/bin/sh?

See above.

> It just starts another occurance of bash.....
> The test above was done when logged in as myself (inaninck) and then
> started a new sh. My login uses:
> inaninck:mypasswd:501:100:Ivo Naninck:/home/inaninck:/bin/bash
> 
> And user kde behaves the same, I guess/hope:
> kde:kdepasswd:508:100:KDEsktop:/home/kde:/bin/bash
>

This is ok the problem is below.
 
>> Hope this helps and gives us more information to work with. I am still
>> convinced it is a shell problem. The kfm file has the offending line in
>> it. It should probably test to see what shell it is being used before
>> executing and then do the right thing based on the shell the user is
>> using.
>> 
> As far as I can see, there is no difference between myself and the user
> 'kde',
> concerning the shell.
> 
> Changing to csh (which is root's shell) gives:
> 
> /home/inaninck> csh
>> set FOO=3; export FOO
> export: Command not found.
>> 
> So that's not an alternative....
> 

The problem is the use of csh for root. The kfmsu and kfmsu2 expects root
to have a bash or bourne shell. It does the su, and then tries to export
and enviroment variable in the bash/sh fashion. But as you point out, root
uses csh. Try changing root's shell to bash instead of csh in the
/etc/passwd file, this should solve your problem.

> Still stuck... :-((
> 
> ---
> Catsup and Mustard all over the place!  It's the Human Hamburger!
> 
> Best regards, and don't let the bits byte!
> Ivo Naninck.
> ~
> ~
>:wq!

Let me know the results of changing root's shell from csh to bash. I think
you will be pleasantly surprised =) One other alternative is to change
kfmsu and kfmsu2 to use csh syntax for setting environment variables.

Cheers,

Bruce...


----------------------------------
E-Mail: Bruce J. Carter <bjcarter@gte.net>
Date: 29-Jun-98
Time: 20:49:18

This message was sent by XFMail
----------------------------------

[prev in list] [next in list] [prev in thread] [next in thread]