this init script fails when the default shell is busybox sh. This
is because busybox sh doesn't set the UID. No other init scripts
in oecore feel the need to check the UID so just remove the check.
(From OE-Core master rev: dd6a45536043af34c05a699e468cef4845f7affd)
(From OE-Core rev: 11385321982411d3d1c2aa663b2b2d195c74f353)
Signed-off-by: Jack Mitchell <jmitchell@cbnl.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Enable PAM support for cronie and update its pam config file 'crond'.
(From OE-Core rev: fec92e4b0c34adc9d512f61ff22de9026b83e3b4)
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
fix [BUGID #673]
several cron related test cases in LTP reveals that our current cron recipe
is not complete:
a) a complete cron hierarchy better have:
/etc/crontab
/etc/cron.d
/etc/cron.hourly
/etc/cron.daily
/etc/cron.weekly
/etc/cron.monthly
b) for a normal user to use crontab command:
add a new group - crontab
/usr/bin/crontab is setgid to root:crontab
/var/spool/cron is owned by root:crontab
below are optional, and thus not included in the default setup:
/etc/cron.deny
/etc/cron.allow
cronie by default only allows root user to use crontab, if neither cron.deny
nor cron.allow exists. They are controlled by final policy deployed on the
product.
Signed-off-by: Kevin Tian <kevin.tian@intel.com>