-
-
Notifications
You must be signed in to change notification settings - Fork 427
RFE: Enhance all drivers with common option to report media type #3322
Copy link
Copy link
Open
Labels
enhancementnut-driver-enumerator (NDE)nut-driver-enumerator (NDE) automates service management integration for NUT driver instances etc.nut-driver-enumerator (NDE) automates service management integration for NUT driver instances etc.portabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possibleservice/daemon start/stopGeneral subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/DebugGeneral subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/Debug
Milestone
Description
Metadata
Metadata
Assignees
Labels
enhancementnut-driver-enumerator (NDE)nut-driver-enumerator (NDE) automates service management integration for NUT driver instances etc.nut-driver-enumerator (NDE) automates service management integration for NUT driver instances etc.portabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possibleservice/daemon start/stopGeneral subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/DebugGeneral subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/Debug
Currently NDE guesses link-related dependencies based on driver name and port value (e.g. localhost or remote dummy-ups). Per recent discussions, there may be other wannabe consumers of such info, like openwrt/packages#28298, so let's make the drivers report it themselves for any given configuration and exit (no conflict with running instance).
Expose also via
ups(svc)drvctl, maybenutconf; refactor NDE scripts (maybe keep current logic as fallback?)