why cron is not running?

English Applications
1

hi
I edit my crontab and write


* * * * * idle3

but it’s not running, for edit crontab i use


EDITOR=/usr/bin/gedit crontab -e

and my OS is OpenSuse 13.1
thank you

2

On Mon 30 Jun 2014 11:56:02 PM CDT, mshj wrote:

hi
I edit my crontab and write

Code:

          • idle3

but it’s not running, for edit crontab i use

Code:

EDITOR=/usr/bin/gedit crontab -e

and my OS is OpenSuse 13.1
thank you

Hi
By default cron knows no environment, you need to set the full path to
your script in your crontab.

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-17-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

3

The environment entry was for editing using crontab, not an entry “in” crontab.

4

I suspect the comment was about “idle3” possibly depending on your PATH setting.

5

run

type idle3

using your shell and whatever is the output you need to put in cron ie

* * * * * /path/to/my/idle3

Assuming that idle3 is in your PATH the builitin **type **is useful, if not you can just put the absolute path of idle3.

6

On 2014-07-01 01:56, mshj wrote:
>
> hi
> I edit my crontab and write
>
> Code:
> --------------------
>
> * * * * * idle3
>
> --------------------
>
> but it’s not running, for edit crontab i use
>
> Code:
> --------------------
>
> EDITOR=/usr/bin/gedit crontab -e
>
> --------------------
>
> and my OS is OpenSuse 13.1
> thank you

Oh. So I suppose that “cron IS running”, but that “your cronjob is not
running”. There is a big difference! :slight_smile:

“cron” is the system daemon or service that runs the “cronjobs” existing
in a system.

Normally when a cronjob fails to work, you get the error message sent to
you via email. Unix/Linux machines are capable of sending emails from
local users to local users, or like in this case, from a program running
without a terminal to a user. In order to read these emails, you
typically use the command “mail” at a terminal. Or configure kmail or
evince or whatever to be able to pick those emails. I use Pine.

Reading that email would tell you the actual reason for not working. But
guessing, it is probably because you have to use “/path/to/my/idle3” as
others have told you.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

7

Hello.
I join this thread because I have the same problem.
After re-reading SDB:Cron - openSUSE Wiki
and spending long time to this problem I have discovered :

crontab -e

open /var/spool/cron/tabs/$USER and put it in a temporary file in directory /tmp, and after exiting, you have yourself put it back to the running directory by typing the following commands :

crontab "/temp/temporary file name"

.
That is not what you could imagine when reading the SD/:Cron

This is the most common way how to user define his cron job. If you want edit cron job just use crontab -e command. It will open preferred (export EDITOR=vim) editor with already defined cronjobs. Each line is represent one cron job definition. With crontab command you could also list your user cronjobs crontab -l.
Crontab definitions are placed in /var/spool/cron/tabs/

But the files in that directory (/var/spool/cron/tabs/$USER) are never run.

So I decide to put the files in /etc/cron.d
And the scripts are run

So where to put user cron script ( even for specific script for root user )

Any comment or correction are welcome.