Skip to content
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

[dev.icinga.com #13163] Fix for traditional glob(3) behaviour #4778

Closed
icinga-migration opened this issue Nov 11, 2016 · 0 comments
Closed
Assignees
Labels
bug Something isn't working
Milestone

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/13163

Created by edgar_fuss on 2016-11-11 11:41:28 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-11-11 11:41:28 +00:00 (in Redmine)

Icinga Version: 2.5.4
Backport?: Not yet backported
Include in Changelog: 1

Traditional (i.e. BSD) glob(3) behavior is, for a pattern foo/*/bar, to stat(2) foo/x/bar even if foo/x is a regular file.
Work around this by passing an error handling function to glob(3) and omitting GLOB_ERR.

Attachments

  • glob.patch edgar_fuss - 2016-11-11 11:41:28 +00:00
@icinga-migration icinga-migration added the bug Something isn't working label Jan 17, 2017
@dnsmichi dnsmichi added this to the 2.7.0 milestone Feb 9, 2017
@dnsmichi dnsmichi self-assigned this Feb 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants