Direct STDERR output when listing crontab to /dev/null

[danielatdattrixdotcom]

Description (*)

When installing crontab on systems using fcron the output from STDERR is captured and inserted into the updated crontab. An example from a fresh install follows. While fcron does not outright complain about this when saving the file, it is messy and quite avoidable.

2019-02-03 13:18:18  INFO listing magento's fcrontab
#~ MAGENTO START 7cd0a74c421051ec6cce8936eb9edd02
* * * * * /usr/lib64/php7.2/bin/php /var/www/magento/bin/magento cron:run 2>&1 | grep -v "Ran jobs by schedule" >> /var/www/magento/var/log/magento.cron.log
* * * * * /usr/lib64/php7.2/bin/php /var/www/magento/update/cron.php >> /var/www/magento/var/log/update.cron.log
* * * * * /usr/lib64/php7.2/bin/php /var/www/magento/bin/magento setup:cron:run >> /var/www/magento/var/log/setup.cron.log
#~ MAGENTO END 7cd0a74c421051ec6cce8936eb9edd02

Fixed Issues (if relevant)

N/A

Manual testing scenarios (*)

1. Use fcron as system cron daemon
2. Execute cron:install command
3. View crontab and see it littered with STDERR output

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)

[magento-engcom-team]

Hi @danielatdattrixdotcom. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento-engcom-team give me test instance - deploy test instance based on PR changes
• @magento-engcom-team give me 2.3-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

[magento-cicd2]

All committers have signed the CLA.

[danielatdattrixdotcom]

@magento-engcom-team give me test instance

[magento-engcom-team]

Hi @danielatdattrixdotcom. Thank you for your request. I'm working on Magento instance for you

[magento-engcom-team]

Hi @danielatdattrixdotcom, here is your new Magento instance.
Admin access: https://pr-20951.instances.magento-community.engineering/admin
Login: admin Password: 123123q

[magento-engcom-team]

Hi @ihor-sviziev, thank you for the review.
ENGCOM-4124 has been created to process this Pull Request

[magento-engcom-team]

@danielatdattrixdotcom thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository.

[magento-engcom-team]

Hi @ihor-sviziev, thank you for the review.
ENGCOM-4124 has been created to process this Pull Request

[sivaschenko]

I was not able to reproduce the issue. STDERR content generated during crontab command execution is not added to the crontab content.
I used an alias to emulate crontab output to STDERR (MacOS): alias crontab='_(){ (>&2 echo "error message" & crontab $1) }; _’

However, I think this pull request should be merged in order to ensure STDERR is not included in the crontab content on specific environments.

[m2-assistant]

Hi @danielatdattrixdotcom, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.