>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 file in /etc, /etc/init.d, /etc/pam.d, ~, but I could find
nothing. I could force it, but I would also like to understand where
this comes from...
Found it! It comes from my .screenrc, where I set shell to "-bash"
instead of "-/bin/bash".
>--- cow-shell.c.~1.5.~ 2005-08-17 08:53:34.000000000 +0900
>+++ cow-shell.c 2005-09-21 22:15:29.000000000 +0900
>@@ -48,9 +48,9 @@
> const char* myshell=getenv("SHELL")?:"/bin/sh";
> fprintf(stderr, "Invoking %s\n", myshell);
>
>- execl(myshell,
>- myshell,
>- NULL);
>+ execlp(myshell,
>+ myshell,
>+ NULL);
> }
> perror("cow-shell: exec");
> return 1;
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
working for years (since 2001 at least).
Thank you.
--
Francesco Potortì (ricercatore) Voice: +39 050 315 3058 (op.2111)
ISTI - Area della ricerca CNR Fax: +39 050 313 8091
via G. Moruzzi 1, I-56124 Pisa Email: [EMAIL PROTECTED]
Web: http://fly.isti.cnr.it/ Key: fly.isti.cnr.it/public.key
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
