Re: [SLE] cron.daily [Was: A bothering "find" in SUSE10]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


The Wednesday 2006-06-28 at 13:13 +0100, Kevin Donnelly wrote:

On Tuesday 27 June 2006 22:43, Carlos E. R. wrote:
Well, the thing is, cron is designed for systems that stay continuously on,
but that is not the case for most home users (and business users should
power off their computers when not used for the environment sake).

I can see the rationale, but it doesn't hold water. If the system is not on
continuously, it is inherently less likely that the tasks need to be run
every 24 hours, so why not let the user choose when he/she wants to run them?

Many (new) users would not know how to program it, nor the need to do it.
As it is, it works. For example, if the computer is off for a week, it
will run when powered up again. If it is on full time, it will not run
oftener than once a day. It's just that, an engineering compromise, a
solution that works in all possible situations, even if not optimum for
many.


People that need to know it, do know it ;-)

Say what??? Awareness through obscurity?? That's what I was getting at, the
idea that you have to be some sort of initiate to know the nous.

I'm (half) joking.

If you are an expert, you know how it works and how to modify it. If you
don't know how, you probably also do not need to touch it.


Otherwise, you ask here, or browse the archive, it's been commented
"hundreds" of times :-p

Well, I've been on this list since 98, and I don't really remember it coming
up all that often before, but maybe I'm getting old.

Again, I'm joking. It's been commented quite often, that I know, but not
"hundreds" :-)


But true, it could be clearly documented, or configured in Yast. There are
settings in Yast to adjust it, in fact.

LOL. These settings (/etc/sysconfig Editor -> Applications -> Locate) allow
you to run it or not, who to run it as, and what paths to include or skip,
but nothing as obvious as a time to run it at, which was the OP's problem.

No, not the time. But it can be disabled there, instead of killing the
job somehow, as some suggested. And there are other jobs like logrotate,
tmp purge, etc, that can be adjusted.

That's my point - it can't be harder to code a time setting than it is to
code one of these settings, and yet nobody seems to have thought to do it :-)

The trick of deleting the flag file is a "hack", but it works. Another
better way would be to modify "/etc/crontab":

- -*/15 * * * * root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1

it would be very simple to program it at a fixed hour, or a range of
hours. Very simple, and easy to find the modification for a new admin.
This could be documented somewhere, of course; but the SuSE manual does
not teach Linux, that is assumed. Probably they thought that admins would
know, and the rest do not need to know - you know, you can not break what
you don't know it exists :-P

- --
Cheers,
Carlos Robinson

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQFEopHutTMYHG2NR9URAvYIAJ4kpcTrt8+kyVed64koFzV5HcQL2wCfdAx9
fG2E8wseteCpma/UkJyW/qI=
=HsHo
-----END PGP SIGNATURE-----


--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx

Relevant Pages

  • Re: Low end desktop for EE tasks?
    ... Not only operating and configuring, but also programming in many cases. ... tinkering with their computers. ... The deal was that once you're an admin, ... Where I am now, everyone (well, all the engineers at least) has two ...
    (sci.electronics.design)
  • Re: XP & W2K server User rights need help
    ... before did not install the apps as admin. ... >behaved app. ... >> server non of the users had accounts only the computers ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Nesting domain groups under local groups
    ... They would have to ask the domain admin to remove them ... application is hard coded to check for permissions in the custom local group ... (or custom domain group). ... They can only do this because they are admins of the computers -- were ...
    (microsoft.public.windows.server.active_directory)
  • Re: Delegation Wizard
    ... >> computers OU Built-In or not!! ... > * Configure the delegation of control wizard as mentioned in the links ... > * create separate admin accounts to perform admin tasks ...
    (microsoft.public.win2000.active_directory)
  • Re: Delegation Wizard
    ... > computers OU Built-In or not!! ... * Configure the delegation of control wizard as mentioned in the links ... * create separate admin accounts to perform admin tasks ... * Create an OU for the Admin roles and the admin tasks ...
    (microsoft.public.win2000.active_directory)