New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: ping fails on servers that don't set PATH in cron #7603

Merged
merged 2 commits into from Nov 1, 2017

Conversation

Projects
None yet
3 participants
@murrant
Member

murrant commented Nov 1, 2017

DO NOT DELETE THIS TEXT

Please note

Please read this information carefully. You can run ./scripts/pre-commit.php to check your code before submitting.

Testers

If you would like to test this pull request then please run: ./scripts/github-apply <pr_id>, i.e ./scripts/github-apply 5926

@murrant murrant changed the title from Find commands to fix: ping fails on servers that don't set PATH in cron Nov 1, 2017

fix: ping fails on servers that don't set PATH in cron
Find the full path to fping and persist it in the database.
Adds the ability to persist settings with Config::set()
Show outdated Hide outdated LibreNMS/Config.php Outdated
Add ability to set webui settings.
No display of for paths, because it would be inconsistent.
@scrutinizer-notifier

This comment has been minimized.

Show comment
Hide comment
@scrutinizer-notifier

scrutinizer-notifier Nov 1, 2017

The inspection completed: 1 new issues, 3 updated code elements

scrutinizer-notifier commented Nov 1, 2017

The inspection completed: 1 new issues, 3 updated code elements

@laf laf merged commit fb45f00 into librenms:master Nov 1, 2017

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
license/cla Contributor License Agreement is signed.
Details

@murrant murrant deleted the murrant:find_commands branch Nov 2, 2017

@lock

This comment has been minimized.

Show comment
Hide comment
@lock

lock bot May 17, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed.

lock bot commented May 17, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed.

@lock lock bot locked as resolved and limited conversation to collaborators May 17, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.