Bug 6458 - crond not working on android due using DEFAULT_SHELL
Summary: crond not working on android due using DEFAULT_SHELL
Status: RESOLVED FIXED
Alias: None
Product: Busybox
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.21.x
Hardware: All Linux
: P5 major
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-16 10:05 UTC by me_a_user
Modified: 2017-07-21 23:48 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description me_a_user 2013-08-16 10:05:14 UTC 
crond is always using DEFAULT_SHELL to execute a scheduled job. Though this is set to /bin/sh which does not exsist on android.

I saw a discussion on a similar topic dated back to 2011. There it was mentioned that on android the system reports the default shell for a user correctly to /system/bin/sh even if there is no passwd file (which usually is the case on android).

At least there should be a way to configure crond maybe what shell to use?
Comment 1 Denys Vlasenko 2017-07-21 23:48:46 UTC 
Fixed in git:

       /* $SHELL, or current UID's shell, or DEFAULT_SHELL */
       /* Useful on Android where DEFAULT_SHELL /bin/sh may not exist */
       G.default_shell = xstrdup(get_shell_name());