Darryl Gregorash wrote:
On 2007-05-09 18:36, Joachim Schrod wrote:
<snip>
No, sorry, not at all. /etc/cron.d/ is *very* valuable.
It is needed if one
(a) wants to be able to install and de-install a cron file without
changing /etc/crontab, e.g., by a package,
In 9.3, non-root users don't have write permission in /etc/cron.d, so
only packages installed by root could create a cron file there.
All packages are installed by root, that's no question.
But there are more packages in the world than SUSE packages.
Some folks, in particular, especially in large IT environments,
package their own local software; to be able to install it
controlled and automatically on a large number of systems.
(the question then is do the entries in cron.d inherit the /etc/crontab
settings?).
No, each crontab file needs the settings anew.
The only advantage I can see to using /etc/cron.d at all (which of
course on some installations might be a tremendous advantage) is that
you can have a separate environment, eg. different MAILTO, for each of
the files.
You discarded the other two reasons that I give. This gives the
impression that you don't find them essential.
So, please tell me: How do you create a cron job that is executed
every 15 minutes and that shall be installed by an rpm package,
without /etc/cron.d/?
You can also tell me if you don't see the need for this requirement.
Joachim
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: [EMAIL PROTECTED]
Roedermark, Germany
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
