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>
We add PACKAGECONFIG[] data for audit and move
the current pam related stuff into it's own entry.
(From OE-Core rev: ada22cab96bb6b7cc98782a14e7c44fbebde77df)
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
crontab is meant to be a system user, not a normal user of the system
so lets pass the correct parameters to the system. If we don't do this
it interferes with the setup of normal users, particularly if some
preset list of users is desired.
(From OE-Core rev: ea6b28cad959d9ebbaf0ecbd695d1d72c0c01151)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is considered good practice to use the build system provided
variables instead of directly specify hardcoded paths.
(From OE-Core rev: 7b13be661c869eb4bf88d16a928a97edd5bc203b)
Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
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>
I've cleaned up some odd license fields, fixed some license
names and corrected some incorrect licenses. LICENSE really needs
a pass through by the maintainers as some of the licensing is
incorrect.
Also, every license with Artistic should be gone through and noted as
which version of Artistic.
(From OE-Core rev: 4786ecdf7cd427089464dcb62579110d494e7cd7)
Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Syslog is full with entries like:
/usr/sbin/crond[773]: (CRON) STAT FAILED (/etc/cron.d): No such file or directory
Checking the package yields
Package cronie (1.4.6-r0) is installed on root and has the following files:
/usr/sbin/crond
/etc/init.d/crond
/usr/bin/crontab
/etc/sysconfig/crond
Which is missing most of what do_install_append installs, this commit fixes that
(From OE-Core rev: 4ba1d06b51d77f4bb1f542ba26328f718161a92a)
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
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>
Jack Mitchell
Joe Slater
Saul Wold
Cristiana Voicu
Richard Purdie
Radu Moisan
Javier Martinez Canillas
Martin Jansa
Wenzong Fan
Dexuan Cui
Beth Flanagan
Koen Kooi
Kevin Tian
Mark Hatle
Saul Wold