[NTLUG:Discuss] DCOP server & KDE 3.

Steve Baker sjbaker1 at airmail.net
Sat Nov 9 09:05:48 CST 2002


MadHat wrote:

>>Right - but 'setenv' does the same thing as 'export' and I'm pretty sure
>>I have everything set up the same.
> 
> same thing yes, same syntax no.  That is what I meant.  Maybe some
> script is expecting bash and running an 'export KEY=var' and you needed
> 'setenv KEY var'.  So it wouldn't catch everything it needed properly.  
> maybe look at the startkde script?  Don't know just thinking outloud.
 >> it shouldn't matter what you are running, because each script should
> point at the proper interpretor.

Right - the shell doesn't choose the interpreter - the exec function (or
maybe the kernel) does that.

The file needs to start with either:

   * The right magic number to say it's a binary executable.
   * A '#!' directive to say that it's interpreted by the specified
     interpreter.
   * Nothing special - in which case the program is started with /bin/sh
     as it's interpreter - and since /bin/sh is a link to /bin/bash under
     Linux, that means that even shell scripts without an explicit
     interpreter directive will be run as bash scripts...no matter what
     your login shell is.

...so this shouldn't be a problem.

>>If only one of these stupid programs would leave a detailed log file - or
>>have a 'verbose' option - or just a more explicit error message.
> 
> now you are just dreaming...  next thing is you might want decent
> logging

Yeah - I know...it's all beyond the current state of the technology,

> Speaking of which, have you looked in .xsession-errors in your home
> dir?.

Yes - it didn't have anything useful.


-- 
---------------------------- Steve Baker -------------------------
HomeEmail: <sjbaker1 at airmail.net>    WorkEmail: <sjbaker at link.com>
HomePage : http://web2.airmail.net/sjbaker1
Projects : http://plib.sf.net    http://tuxaqfh.sf.net
            http://tuxkart.sf.net http://prettypoly.sf.net





More information about the Discuss mailing list