Project

General

Profile

Actions

Bug #14559

closed

Invalid cron file put by packaging

Added by Nicolas CHARLES about 5 years ago. Updated over 4 years ago.

Status:
Released
Priority:
N/A
Category:
Packaging
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:

Description

The cron file set up via packaging contains

# Cron file for Rudder
#
# Will manually run cf-agent in case cf-execd is no longer running. cf-agent will fire up a new cf-execd.
#
# To temporarily avoid this behaviour, run 'rudder agent disable'

{{#classes.slackware}}
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /opt/rudder/bin/rudder agent check -q >> /var/log/rudder/agent-check/check.log 2>&1
{{/classes.slackware}}
{{^classes.slackware}}
0,5,10,15,20,25,30,35,40,45,50,55 * * * * root /opt/rudder/bin/rudder agent check -q >> /var/log/rudder/agent-check/check.log 2>&1
{{/classes.slackware}}

It is put by packaging
cp ./rudder-sources/rudder-techniques/techniques/system/common/1.0/rudder-agent-community-cron ./rudder-agent.cron
$(INSTALL) -m 644 rudder-agent.cron $(DESTDIR)/etc/cron.d/rudder-agent

we shoudl either have a specific cron, ot strips lines


Subtasks 2 (0 open2 closed)

Bug #16012: error at run of rudder-agent once it's bootstrapped (and invalid cron) on Debian 9ReleasedFélix DALLIDETActions
Bug #16020: Don't edit the cron file in the initial policiesReleasedFélix DALLIDETActions
Actions

Also available in: Atom PDF