Strange behaviour of cron

[Friedhelm Neyer]

Hi together

maybe it's only a syntax error, but the following find runs fine on
commandline but when starting via cron, it fails

find /dir/dir/dir/ -name file -mtime +2 -exec mv {} /dir/dir/dir/file \;

What is wrong here?

Thx in advance
Friedhelm

[Blazej Antczak]

Friedhelm Neyer pisze:

> Hi together
>
> maybe it's only a syntax error, but the following find runs fine on
> commandline but when starting via cron, it fails
>
> find /dir/dir/dir/ -name file -mtime +2 -exec mv {} /dir/dir/dir/file \;
>

^^^^^^^^^^^^^^^^^
what you need that
for? Will work without this as well.

Did you using find with absolute path in cron's script? Put into your
script verbosity (like set -x as second line --> depends from shell).
Log std output and error from this command from cron to some file(s).
Maybe this can point you where error is.

Rgrds,
Blazej

[Friedhelm Neyer]

Blazej Antczak schrieb:

What I want to do is to identify a specific logfile in my homedir, which
will be written every day. To prevent myhome from going out of space I
want to move the logfile, which is older than two days, to another,
bigger directory. So I try to identify the file and move it to another
place. For example

find /my/home -name logfile -mtime +2 exec mv {} \; ???????
==> which syntax to move /my/home/logfile to another dir

[Hajo Ehlers]

On Oct 30, 7:25 pm, Friedhelm Neyer <Friedhelm.Ne...@t-online.de>
wrote:

You must escape the \

find /dir/dir/dir/ -name file -mtime +2 -exec mv {} /dir/dir/dir/file \

\;

hth
Hajo