From wtopa@ix.netcom.com Sat Feb 14 03:45:40 1998
From: wtopa@ix.netcom.com
To: users@lists.opensuse.org
Subject:
 Re: [wtopa@ix.netcom.com: [S.u.S.E. Linux] CORRECTION TkInfo & Cron.daily !!]
Date: Sat, 14 Feb 1998 04:45:40 +0100
Message-ID: <6c3414$tbo$1@Galois.suse.de>
In-Reply-To:
 <[wtopa@ix.netcom.com: [S.u.S.E. Linux] CORRECTION TkInfo & Cron.daily !!]>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0903082291303486889=="

--===============0903082291303486889==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable




        Subject: Re: [wtopa(a)ix.netcom.com: [S.u.S.E. Linux] CORRECTION TkIn=
fo & Cron.daily !!]
        Date: Fri, Feb 13, 1998 at 05:29:00PM -0800

In reply to:Bodo Bauer

Quoting Bodo Bauer(bb(a)suse.com):
>=20
>=20
> Hi Wayne,
> >=20
> >   It probably is, but as I pointed out in the original post, the call
> > to cron.daily is commented out in /sbin/init.d/boot.  WHY??  OK, now
> > for us dummies, if it (cron.daily) is NOT called by /sbin/init.d/boot
> > WHAT DOES call it? Yes I see that cron.daily is in the /etc/crontab
> > script but how does that run.  Who/What calls /etc/crontab. It isn't
> > clear, to me, and no one has come forward to explain it.  I have asked
> > the same question more than once.  It is not in the book!   The man
> > page included in SuSE 5.1 covers the crontab -e method only.  Why has
> > SuSe changed methods and not included the relavent man pages?
>=20
> man cron says:
>=20
> [...]
>        Cron  searches  /var/cron/tabs for crontab files which are
>        named after accounts in /etc/passwd;  crontabs  found  are
>        loaded  into  memory.  Cron also searches for /etc/crontab
>        which is in a different  format  (see  crontab(5)).   Cron
>        then wakes up every minute, examining all stored crontabs,
>        checking each command to see if it should be  run  in  the
>        current  minute.   When  executing commands, any output is
>        mailed to the owner of the crontab (or to the  user  named
>        in the MAILTO environment variable in the crontab, if such
>        exists).
> [...]
>=20
> As you see /etc/crontab is not assigned to any user, it's kind
> of a 'system' table for regular jobs.=20
>=20
> I think it's not a question of SysV or not, it's just an
> additional file to place jobs for regular sceduling. The
> line in /sbin/init.d/boot is usefull if your isn't up 24h.
>=20
> crontab -e works still like it's supposed to be. You can
> have a crontab for root and any other user...
>=20
Bodo

  How stupid of me.  Why did I only look for information on crontab
in crontab Man pages.  I should have looked in cron.  ;-((

  Ok, so I guess that any cron jobs should be put in /etc/crontab. Now
may I ask, what are the advantages f any, over crontab -e?

wayne
> Cioa,
> 	BB
> --=20
> Bodo Bauer          S.u.S.E., LLC                    fon +1-510-835 7873=20
> bb(a)suse.de          458 Santa Clara Avenue           fax +1-510-835 7875
> <A HREF=3D"http://www.suse.com"><A HREF=3D"http://www.suse.com</A">http://w=
ww.suse.com</A</A>>  Oakland CA, 94610  USA
> --
> To get out of this list, please send email to majordomo(a)suse.com with
> this text in its body: unsubscribe suse-linux-e
>=20
> .


--=20
Real computer scientists don't comment their code.  The identifiers are
so long they can't afford the disk space.
_______________________________________________________
Wayne T. Topa <wtopa(a)ix.netcom.com>
--
To get out of this list, please send email to majordomo(a)suse.com with
this text in its body: unsubscribe suse-linux-e


--===============0903082291303486889==--