cron(8) improvement

George Mitchell george+freebsd at m5p.com
Sun Nov 10 14:04:21 UTC 2013


On 11/09/13 21:23, Allan Jude wrote:
> On 2013-11-09 21:13, Adrian Chadd wrote:
>> On 9 November 2013 17:58, Allan Jude <freebsd at allanjude.com> wrote:
>>
>>> Well, if the rc.conf config is specific to the daemon being installed by
>>> the package, then the existing /etc/rc.conf.d/ system works fine, it
>>> just falls down a little on xorg configuring hald, unless you just make
>>> the xorg package create /etc/rc.conf.d/hald and /etc/rc.conf.d/dbus
>> If I install hal/dbus, why wouldn't they themselves populate
>> /etc/rc.conf.d/hald and /etc/rc.conf.d/dbus ?
>>
>> If there are hal/dbus options that need configuring by other packages,
>> then sure, you'll need to add some other things too.
> ahh, right, why didn't I think of that
>
>>> I like the simplicity of rc.conf, and I would much rather not involve an
>>> sqlite database, I am not sure how that could possibly be faster then
>>> sourcing an extra shell script.
>> Don't focus on that. The sqlite example is just that - an example -
>> showing what kind of operations you would want to implement to _allow_
>> you to do that. I'm not advocating for doing it in freebsd-base.
>>
>> The point I'm making is this:
>>
>> * when populating rc.conf.d/, don't just do 'cp' in a post-install script
>> * when populating the cron daemon entries in rc.cron.d, don't just
>> 'cp' in a post-install script.
>>
>>
>> -adrian
>
> If the cron daemon is just scanning /etc/cron.d/* and treating it as if
> those lines had been appended to /etc/crontab I don't see why you
> couldn't just cp in the post-install. I think it would be better if you
> didn't have to 'register' a change.
>
>

For this whole thread, please s,/etc/rc.d,/usr/local/etc/rc.d,g
-- George


More information about the freebsd-current mailing list