-
Notifications
You must be signed in to change notification settings - Fork 4
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
Nut driver enumerator optimize (FTY) #81
base: FTY
Are you sure you want to change the base?
Conversation
…led to add a normally-named one because it already exists (clean it up and then add)
…about yet-missing property
…sh the non-instance service (for global config)
…about yet-missing property
… setter into smf_setSavedUniq() for other use-cases
…avoid variable pollution in caller
…" for better readability
…up --get-device-for-service processing where possible
…up --get-device-for-service processing where possible (typo fix)
…r faster --get-service-for-device processing
…F FMRIs more intensively
…ceName data to be consistent (ensuring it is is expensive and belongs elsewhere)
…and upslist_savednames_find_mismatch() to upgrade entries without saved names
…e) and get_device_for_service() into routines
…ssing() into single-run and daemonized modes, to update inconsistent configs
…onfigure() into a routine
…--daemon-after mode
DNMY : As agreed, we'll run a test with a system that has many (hundreds range) driver sections defined to measure if this PR brings benefits, and to estimate where to go next in this area. Points of interest:
|
…uotes around returned DEVICE == "..." value
… smf_setSavedUniq() and smf_setSavedMD5()
…turn expected values
…ceName and hook_getSavedDeviceName
Note: There are some further improvements staged in a development repo at https://github.com/jimklimov/nut/tree/FTY-upssvc-201904 and not yet PRed because the updated codepaths are not yet integrated with the main codebase to replace earlier implementations. When scheduling allows, I'd proceed on that. |
…ot active for simple and daemon modes currently)
The 42ity equivalent to networkupstools#682, without the older improvements which are in FTY and are not yet in upstream (part of 682 now).