[BusyBox] [patch] ash tryexec() problem with shell scripts
Vladimir N. Oleynik
dzo at simtreas.ru
Mon Sep 1 10:59:48 UTC 2003
Jean,
> "Vladimir N. Oleynik" <dzo at simtreas.ru> writes:
>
>
>>Jean,
>>
>>
>>>>I can`t reproduce your problem.
>>>
>>>Try the following:
>>
>>># pwd
>>>/
>>># echo "echo argh" > bin/file_in_your_path
>>># chmod +x bin/file_in_your_path
>>># type file_in_your_path
>>>file_in_your_path is a tracked alias for /bin/file_in_your_path
>>># file_in_your_path
>>>/bin/sh: Can't open file_in_your_path
>>
>>Have you "r" permision?
>
>
> Yes. I create my files with read permissions for myself :).
FALSE!
$ grep -B 3 "Can't open" ash.c
You can see: this message generated if cannot open script file for read.
> Have you tried the small code snipped? It should clearly show the problem. If I
> pass the absolute path to /bin/sh (my suggested patch), it works.
3-th:
I can`t reproduce your problem.
My ash version without your patch run your test fine.
Have you FEATURE_SH_STANDALONE_SHELL or FEATURE_SH_APPLETS_ALWAYS_WIN?
--w
vodz
More information about the busybox
mailing list