Crontab error

Re all,

i’ve setup the crontab to clean the Mason files…

0 * * * * find /opt/rt2/WebRT/sessiondata -type f -amin +600 -exec rm {};

note the -type instead of --type which is written in README, if i use
–type i get wrong parameter, man pages of find point to -type not
–type (typo in README, or slackware difference, tho i doubt)!

I get crontab errors for -exec anyone has an idea?

cron: find /opt/rt2/WebRT/sessiondata -type f -amin +600 -exec rm {};
find: missing argument to `-exec’

Thanks in advance,
A.

Alesh Mustar wrote:

cron: find /opt/rt2/WebRT/sessiondata -type f -amin +600 -exec rm {};
find: missing argument to `-exec’

Put a space between the {} and the ;.

You’re correct about the “-type” typo, by the way. It’s already
fixed in the README for 2.0.2test1.

| cron: find /opt/rt2/WebRT/sessiondata -type f -amin +600 -exec rm {};
| find: missing argument to `-exec’
±–>8

You need a space before the semicolon, and you need to quote the baces to
keep bash from performing brace expansion of an empty list. ("-exec rm
’{}’ ‘;’")

brandon s. allbery [os/2][linux][solaris][freebsd] allbery@kf8nh.apk.net
system administrator [JAPH][WAY too many hats] allbery@ece.cmu.edu
electrical and computer engineering KF8NH
carnegie mellon university [linux: proof of the million monkeys theory]

Sorry about that. the docs should be fixed for 2.0.2On Thu, Jul 19, 2001 at 04:35:57PM +1000, Phil Homewood wrote:

Alesh Mustar wrote:

cron: find /opt/rt2/WebRT/sessiondata -type f -amin +600 -exec rm {};
find: missing argument to `-exec’

Put a space between the {} and the ;.

You’re correct about the “-type” typo, by the way. It’s already
fixed in the README for 2.0.2test1.


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

“It’s buried in the desert, got sand in it, melts Nazis. You know,
the Ark of the Covenant” – siva