|
From: Kari M. <kar...@tr...> - 2006-11-20 22:11:29
|
Dick Middleton wrote:
> Bruce Smith wrote:
>>>> Do either of those packages start by _default_ when you boot DL?
>>>>
>>> Yes. Any program/script placed in /etc/cron.daily for example will be executed
>>> as root. So far as I know this is the only way aide is executed. Had aide
>>> install been good then everybody would be running it whether they wanted to or
>>> not. There's a thing called logwatch also arrived in this DL version which does
>>> work. It is also started in cron.daily. First I knew about it was its report
>>> in my inbox.
>>>
>> OK, maybe the line in the crontab should be commented out by default.
>> (I'll leave that decision to Heiko)
> >
>> OTOH, the last time I checked, crond itself doesn't start by default.
>> And if/when you turn on cron, you it's a good idea to edit/check the
>> crontabs.
>
> I think this is uncovering more than I intended but since we've started, in my
> opinion DL should not have scripts for packages installed in cron.daily etc.
> Instead I suggest it should place them in some other directory. It should then
> create symbolic links from cron.daily to the script at bootup if the package is
> enabled in sysconfig/config. Then it's similar to the way init.d works. That
> way DL retains some visibility and control of what is enabled and does not risk
> activating scripts unintentionally or unexpectedly.
I have to disagree on this, at least somewhat. First, it is customary
for people to make at least some changes to the scripts in cron.* dirs.
They have to remain writable. Second, creating automation to enable
certain links/scripts when a service is activated in
/etc/sysconfig/config, is, to my mind, wasting resources. You would,
for example have to specify wether to make the link into
cron.{hourly|daily|weekly|monthly|d}...
The Germans say, "Nein danke", and I say no thanks, too.
> Dick
-Kari ..not from Germany :-|
|