From: Saul Wold <saul.wold@intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "poky@pokylinux.org" <poky@pokylinux.org>
Subject: Re: [PATCH 2/5] cronie: enable multi-user crontab usage and make cron environment complete
Date: Thu, 27 Jan 2011 16:34:10 -0800 [thread overview]
Message-ID: <4D420F02.8050306@intel.com> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1504DB5E056FB@shsmsx502.ccr.corp.intel.com>
On 01/27/2011 04:07 PM, Tian, Kevin wrote:
>> From: Wold, Saul
>> Sent: Friday, January 28, 2011 2:00 AM
>>> +
>>> +pkg_postinst_${PN} () {
>>> + if [ "x$D" != "x" ] ; then
>>> + exit 1
>>> + fi
>>> +
>>> + # below setting is necessary to allow normal user using crontab
>>> +
>>> + # add 'crontab' group and setgid for crontab binary
>>> + grep crontab /etc/group || addgroup crontab
>>> + chown root:crontab /usr/bin/crontab
>>> + chmod 2755 /usr/bin/crontab
>>> +
>>> + # allow 'crontab' group write to /var/spool/cron
>>> + chown root:crontab /var/spool/cron
>>> + chmod 770 /var/spool/cron
>>> +
>>> + chmod 600 /etc/crontab
>>> }
>> Kevin,
>>
>> I am going to hold off pulling this and the at changes.
>>
>> Is there a specific reason that you are creating this as a post install
>> operation for the permission management, both this and the at recipes
>> are doing this. Please remember that adding additional items that run
>> at first boot slow things down.
>>
>> Is it possible to run these permission changes at actual install time,
>> instead of on the target.
>>
>
> I thought about this when baking the patch, and finally went to this way because
> there's chown operation and new group needs to be created. This has to be done
> on the target, as you'll see in other similar recipes like dbus, hal, ...
>
Since this is a similar theme, is there a bbclass or method that could
be written in order to handle adding users/groups to the passwd/group
file during sysroot creation time, prior to packaging?
Will pseudo handle this correctly?
Maybe for 1.0 we go this route, but we should think more about this, in
order to create the users and groups we need.
I think Ke may run into this also for the rootless X work he is doing.
Sau!
> Thanks
> Kevin
>
next prev parent reply other threads:[~2011-01-28 0:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b7da2f$q8ksnl@fmsmga001.fm.intel.com>
2011-01-27 18:00 ` [PATCH 2/5] cronie: enable multi-user crontab usage and make cron environment complete Saul Wold
2011-01-28 0:07 ` Tian, Kevin
2011-01-28 0:34 ` Saul Wold [this message]
2011-01-28 1:16 ` Yu Ke
2011-01-28 1:18 ` Tian, Kevin
2011-02-01 0:31 ` Saul Wold
2011-02-01 1:03 ` Tian, Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D420F02.8050306@intel.com \
--to=saul.wold@intel.com \
--cc=kevin.tian@intel.com \
--cc=poky@pokylinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.