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 #10231] MkDirP not working on Windows #3442
Comments
Updated by mfriedrich on 2016-02-24 22:49:50 +00:00
|
Updated by mfriedrich on 2016-03-03 08:24:58 +00:00
|
Updated by mfriedrich on 2016-03-03 12:45:28 +00:00 2.4.3 throws an exception.
|
Updated by mfriedrich on 2016-03-03 14:37:23 +00:00 Fix and some (to be removed) debug output. The culprit is the "/" on Windows, the win32 api functions provide support for both, slash and backslash notation. Find() does not ;-)
|
Updated by mfriedrich on 2016-03-03 15:00:06 +00:00
Applied in changeset d14477c. |
Updated by mfriedrich on 2016-03-07 08:21:46 +00:00
|
Updated by mfriedrich on 2016-03-07 08:25:05 +00:00
Applied in changeset 65cbf04. |
Updated by mfriedrich on 2016-03-11 14:51:17 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10231
Created by mfrosch on 2015-09-28 13:53:20 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2016-03-07 08:25:05 +00:00)
Target Version: 2.4.4
Last Update: 2016-03-11 14:51:17 +00:00 (in Redmine)
I call it the "mkdir --no-parents" problem.
Lets say I have a file structure like this:
When there is no non-empty file inside satellite/test/, the config sync silently fails, while not creating even the directory "test".
Looks like while trying to create directories for files, we not handle a non existing parent directory.
This only happens on Windows as far as I tested it...
Basically the agent is looping while refreshing the config and reloading itself:
Attachments
Changesets
2016-03-03 14:54:35 +00:00 by mfriedrich d14477c
2016-03-07 08:22:07 +00:00 by mfriedrich 65cbf04
2016-03-11 14:50:57 +00:00 by mfriedrich 9e833d7
2016-03-11 14:51:08 +00:00 by mfriedrich baecdc3
Relations:
The text was updated successfully, but these errors were encountered: