Hi,
> I think it is okay, unless you decide that having a relative path for
> the shell is a security risk and you don't want to support this. But
> yours would be the only program (as far as I am aware) that chuckles on
> this problem. As I said, before correcting it now, I had this mistake
> w
>What's wrong with your configuration is that you have
>'bash' as SHELL, and not a full path.
Wow! I have had this for years (this is an old installation,
contiunuously updated), and only now I discover this!
I have no idea where the problem comes from. I looked for the "SHELL"
string in all f
Hi,
> $ cow-shell
> Invoking bash
> cow-shell: exec: No such file or directory
What's wrong with your configuration is that you have
'bash' as SHELL, and not a full path.
Where is the environment variable set on your system?
A workaround would be the following patch:
--- cow-shell.c.~1.5.~
>> $ cp -al src test
>>
>> $ cd test
>>
>> $ cow-shell
>> Invoking bash
>> cow-shell: exec: No such file or directory
>>
>> $ type cow-shell
>> cow-shell is hashed (/usr/bin/cow-shell)
>
>
>What's your '$SHELL' ?
$ echo $SHELL
bash
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subjec
Hi,
> Here is what I get:
>
>
> $ cp -al src test
>
> $ cd test
>
> $ cow-shell
> Invoking bash
> cow-shell: exec: No such file or directory
>
> $ type cow-shell
> cow-shell is hashed (/usr/bin/cow-shell)
What's your '$SHELL' ?
regards,
junichi
--
To UNSUBSCRIBE, email to [EMAI
Package: cowdancer
Version: 0.4
Severity: grave
Here is what I get:
$ cp -al src test
$ cd test
$ cow-shell
Invoking bash
cow-shell: exec: No such file or directory
$ type cow-shell
cow-shell is hashed (/usr/bin/cow-shell)
-- System Information:
Debian Release: testing/unstable
APT prefe
6 matches
Mail list logo
