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

Want a general "driver.state" machine reporting for fun and profit #1767

Closed
jimklimov opened this issue Jan 4, 2023 · 0 comments · Fixed by #1771
Closed

Want a general "driver.state" machine reporting for fun and profit #1767

jimklimov opened this issue Jan 4, 2023 · 0 comments · Fixed by #1771
Assignees
@aquette
Labels
documentation feature NUT protocols service/daemon start/stop General subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/Debug
Milestone
2.8.1

Comments

@jimklimov
Copy link
Member

jimklimov commented Jan 4, 2023 •
edited
Loading

On profit side, this would help code "know" if the device is currently (re?)initializing or doing a regular data walk. This in turn can impact some logical behavior (error-handling, reporting, etc.) such as for #1756

On the fun side, we would see if the driver is currently responsive or e.g. doing I/O, via clients as well as debug-logs for troubleshooting.

UPDATE: Seems to duplicate #1388 to an extent
@jimklimov jimklimov added feature documentation service/daemon start/stop General subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/Debug NUT protocols labels Jan 4, 2023
@jimklimov jimklimov added this to the 2.8.1 milestone Jan 4, 2023
jimklimov added a commit to jimklimov/nut that referenced this issue Jan 5, 2023
@jimklimov
drivers/main.c, docs/nut-names.txt: introduce "driver.state" tracking […
2032a0e 
…networkupstools#1767]
jimklimov added a commit to jimklimov/nut that referenced this issue Jan 5, 2023
@jimklimov
drivers/main.c: report where driver.state changes from init.* to just…
ef65497 
… before regular work [networkupstools#1767]
jimklimov added a commit to jimklimov/nut that referenced this issue Jan 5, 2023
@jimklimov
driver/*.c: report reconnection attempts as a "driver.state" [network…
a250ccd 
…upstools#1767]
jimklimov added a commit to jimklimov/nut that referenced this issue Jan 5, 2023
@jimklimov
NEWS: announce new "driver.state" feature [networkupstools#1767]
3a3deee
jimklimov added a commit to jimklimov/nut that referenced this issue Jan 5, 2023
@jimklimov
fixup! driver/*.c: report reconnection attempts as a "driver.state" [n…
771d66d 
…etworkupstools#1767]
jimklimov added a commit to jimklimov/nut that referenced this issue Jan 5, 2023
@jimklimov
driver/*.c: report reconnection attempts as a "driver.state" [network…
2033b97 
…upstools#1767]
jimklimov added a commit to jimklimov/nut that referenced this issue Jan 5, 2023
@jimklimov
NEWS: announce new "driver.state" feature [networkupstools#1767]
7950e28
@jimklimov jimklimov mentioned this issue Jan 5, 2023
Merged
jimklimov added a commit to jimklimov/nut that referenced this issue Jan 5, 2023
@jimklimov
drivers/main.c, docs/nut-names.txt: introduce "driver.state" tracking […
800fa8f 
…networkupstools#1767]
jimklimov added a commit to jimklimov/nut that referenced this issue Jan 5, 2023
@jimklimov
drivers/main.c: report where driver.state changes from init.* to just…
b4887df 
… before regular work [networkupstools#1767]
jimklimov added a commit to jimklimov/nut that referenced this issue Jan 5, 2023
@jimklimov
driver/*.c: report reconnection attempts as a "driver.state" [network…
4c3f6a5 
…upstools#1767]
jimklimov added a commit to jimklimov/nut that referenced this issue Jan 5, 2023
@jimklimov
NEWS: announce new "driver.state" feature [networkupstools#1767]
21b1aea
jimklimov added a commit to jimklimov/nut that referenced this issue Jan 5, 2023
@jimklimov
drivers/main.c, docs/nut-names.txt: introduce "driver.state" tracking […
10be1a9 
…networkupstools#1767]
jimklimov added a commit to jimklimov/nut that referenced this issue Jan 5, 2023
@jimklimov
drivers/main.c: report where driver.state changes from init.* to just…
4afb5e1 
… before regular work [networkupstools#1767]
jimklimov added a commit to jimklimov/nut that referenced this issue Jan 5, 2023
@jimklimov
driver/*.c: report reconnection attempts as a "driver.state" [network…
3ad2474 
…upstools#1767]
jimklimov added a commit to jimklimov/nut that referenced this issue Jan 5, 2023
@jimklimov
NEWS: announce new "driver.state" feature [networkupstools#1767]
0a0c941
@jimklimov jimklimov mentioned this issue Jan 5, 2023
Merged
@jimklimov jimklimov mentioned this issue Apr 18, 2023
Closed
This was referenced May 28, 2023
Open
Closed
jimklimov added a commit to jimklimov/nut that referenced this issue Jun 30, 2023
@jimklimov
Bump all driver versions before NUT v2.8.1 release [networkupstools#1951
aca017f 
]

Follow-up after core driver changes (main.c etc.) with `driver.state` networkupstools#1767,
driver reload command networkupstools#1903, driver inter-instance communications via socket networkupstools#1922
and others.

Also convert remaining single-digit X.Y versions to X.<Y+1>0 double-digits.
@jimklimov jimklimov mentioned this issue Jun 30, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aquette aquette

Labels
documentation feature NUT protocols service/daemon start/stop General subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/Debug
Projects
None yet
Milestone
2.8.1
Development

Successfully merging a pull request may close this issue.

Introduce driver.state tracking jimklimov/nut
2 participants
@aquette @jimklimov