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.
> >> (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. -- Moral indignation is jealousy with a halo. -- HG Wells -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
