User story #6580: Cron technique: add an option to support "prevent cron from writing a syslog message about this command getting executed" option - Rudder - Issue Tracker

Actions

Copy link

User story #6580

open

Cron technique: add an option to support "prevent cron from writing a syslog message about this command getting executed" option

Added by Florian Heigl over 9 years ago. Updated almost 7 years ago.

Status:

New

Priority:

N/A

Assignee:

Category:

Techniques

Target version:

Ideas (not version specific)

Pull Request:

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

Description

Hi,

I found the cron standard rudder technique has problems with more complex time specifications.

The literal example for testing follows:

#activity reports every 10 minutes everyday -*/10 * * * * root /usr/lib64/sa/sa1 #update reports every 6 hours 0 */6 * * * root /usr/lib64/sa/sa2 -A

No biggie but I think at some point the validation here needs to be reviewed.

Files

rudder_cron.jpg (88.3 KB) rudder_cron.jpg

Florian Heigl, 2015-05-12 17:46

Actions

Copy link

Updated by Benoît PECCATTE over 9 years ago

Sorry, I don't understand where the problem lies.
What doesn't work with your example ?

Actions

Copy link

Updated by Florian Heigl over 9 years ago

File rudder_cron.jpg rudder_cron.jpg added

Hi Benoit,

it'll produce following error:

'Please modify Manually defined frequency to match the requested format : Please enter a valid cron interval'[[]]

Actions

Copy link

Updated by Florian Heigl over 9 years ago

Actions

Copy link

Updated by Benoît PECCATTE over 9 years ago

I didn't know the syntax -* what does it mean ?
I can't find it in the manual.

Actions

Copy link

Updated by Florian Heigl over 9 years ago

I also didn't know this one. I just knew it was working :)

docs say:
"If the uid of the owner is 0 (root), he can put a "-" as first character of a crontab entry. This will prevent cron from writing a syslog message about this command getting executed."
What a great feature for those spamming jobs.

crontab(5) for cron - daemon to execute scheduled commands (ISC Cron V4.1)

But even just using the */3 syntax seems to trip it.

Actions

Copy link

Updated by Benoît PECCATTE over 9 years ago

Category set to Techniques
Target version set to 2.10.14

oO
OK, but the */3 works for me.

Actions

Copy link

Updated by Vincent MEMBRÉ over 9 years ago

Target version changed from 2.10.14 to 2.10.15

Actions

Copy link

Updated by Vincent MEMBRÉ over 9 years ago

Target version changed from 2.10.15 to 2.10.16

Actions

Copy link

Updated by Vincent MEMBRÉ over 9 years ago

Target version changed from 2.10.16 to 2.10.17

Actions

Copy link

#10

Updated by Vincent MEMBRÉ about 9 years ago

Target version changed from 2.10.17 to 2.10.18

Actions

Copy link

#11

Updated by Vincent MEMBRÉ about 9 years ago

Target version changed from 2.10.18 to 2.10.19

Actions

Copy link

#12

Updated by Vincent MEMBRÉ about 9 years ago

Target version changed from 2.10.19 to 2.10.20

Actions

Copy link

#13

Updated by Vincent MEMBRÉ almost 9 years ago

Target version changed from 2.10.20 to 277

Actions

Copy link

#14

Updated by Vincent MEMBRÉ almost 9 years ago

Target version changed from 277 to 2.11.18

Actions

Copy link

#15

Updated by Vincent MEMBRÉ almost 9 years ago

Target version changed from 2.11.18 to 2.11.19

Actions

Copy link

#16

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 2.11.19 to 2.11.20

Actions

Copy link

#17

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 2.11.20 to 2.11.21

Actions

Copy link

#18

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 2.11.21 to 2.11.22

Actions

Copy link

#19

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 2.11.22 to 2.11.23

Actions

Copy link

#20

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 2.11.23 to 2.11.24

Actions

Copy link

#21

Updated by Vincent MEMBRÉ about 8 years ago

Target version changed from 2.11.24 to 308

Actions

Copy link

#22

Updated by Vincent MEMBRÉ about 8 years ago

Target version changed from 308 to 3.1.14

Actions

Copy link

#23

Updated by Vincent MEMBRÉ about 8 years ago

Target version changed from 3.1.14 to 3.1.15

Actions

Copy link

#24

Updated by Vincent MEMBRÉ about 8 years ago

Target version changed from 3.1.15 to 3.1.16

Actions

Copy link

#25

Updated by Vincent MEMBRÉ about 8 years ago

Target version changed from 3.1.16 to 3.1.17

Actions

Copy link

#26

Updated by Vincent MEMBRÉ almost 8 years ago

Target version changed from 3.1.17 to 3.1.18

Actions

Copy link

#27

Updated by Vincent MEMBRÉ almost 8 years ago

Target version changed from 3.1.18 to 3.1.19

Actions

Copy link

#28

Updated by Benoît PECCATTE over 7 years ago

Subject changed from cron technique to cron technique form input error

Actions

Copy link

#29

Updated by Jonathan CLARKE over 7 years ago

Tracker changed from Bug to User story
Subject changed from cron technique form input error to Cron technique: add an option to support "prevent cron from writing a syslog message about this command getting executed" option

Florian Heigl wrote:

I also didn't know this one. I just knew it was working :)

docs say:
"If the uid of the owner is 0 (root), he can put a "-" as first character of a crontab entry. This will prevent cron from writing a syslog message about this command getting executed."
What a great feature for those spamming jobs.

Wow, I had no idea that option existed. Nice find.

However, it is not actually related to the job frequency, so I think that it is correct that the Technique does not support it. I'm transforming this ticket into a user story so we can add an option to allow for this, it would be something like "Prevent cron from writing a syslog message about this command getting executed", that would add the "-" in front of the frequency, if the user is root.