Project

General

Profile

Actions

Bug #5921

closed

Rudder cron entries contain legacy entries

Added by Matthieu CERDA over 9 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
1
Assignee:
-
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

We still have this in cron:

0,5,10,15,20,25,30,35,40,45,50,55 * * * * root . /etc/profile; if [ -e ${g.rudder_base}/bin/check-rudder-agent ]; then ${g.rudder_base}/bin/check-rudder-agent; else if [ ! -e ${g.rudder_base}/etc/disable-agent -a `ps -efww | grep -E "(cf-execd|cf-agent)" | grep -E "${sys.workdir}/bin/(cf-execd|cf-agent)" | grep -v grep | wc -l` -eq 0 ]; then ${sys.workdir}/bin/cf-agent -f failsafe.cf >/dev/null 2>\&1 \&\& ${sys.workdir}/bin/cf-agent >/dev/null 2>\&1; if [ $? != 0 ]; then if [ -f /opt/rudder/etc/rudder-restart-message.txt ]; then cat /opt/rudder/etc/rudder-restart-message.txt; else echo "Rudder agent was unable to restart on ${hostname}."; fi; fi; fi; fi

I think the 3.0 is a good occasion to get rid of this and only use check-rudder-agent...


Related issues 1 (0 open1 closed)

Is duplicate of Rudder - Architecture #5391: Replace complex cron one-liner with one script call (impl)ReleasedBenoƮt PECCATTE2014-08-14Actions
Actions #1

Updated by Jonathan CLARKE over 9 years ago

  • Status changed from In progress to Rejected

This has already been done in #5391.

Actions

Also available in: Atom PDF