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.

Sign up for GitHub

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

Jump to bottom

write objects.precache in tmp file first, then move it #439

Merged
merged 2 commits into from
Oct 13, 2023
Merged

write objects.precache in tmp file first, then move it #439

merged 2 commits into from
Oct 13, 2023

Commits on Oct 12, 2023

  1. write objects.precache in tmp file first, then move it 

    It's a good standard to do so and in fact, we do this already in several
places, ex. the status.dat. This ensures the file is ready and completly
written before it will be used.

The issue here is, that naemon starts without any issues if the precached file
is empty for any reason. Except it has zero hosts/services then and removes all
existing states/downtime/comments.

Signed-off-by: Sven Nierlein <[email protected]>
    @sni
    sni committed Oct 12, 2023
    Configuration menu
    Copy the full SHA
    e75cc3d View commit details
    Browse the repository at this point in the history

Commits on Oct 13, 2023

  1. fix typo in comment 

    left over from copy/pasted code.
    @sni
    sni committed Oct 13, 2023
    Configuration menu
    Copy the full SHA
    7a72350 View commit details
    Browse the repository at this point in the history