Skip to content

[DO NOT MERGE] Reference: https://github.com/networkupstools/nut/pull/473#39

Closed
geraldguillaume wants to merge 1 commit into42ity:FTYfrom
geraldguillaume:FTY
Closed

[DO NOT MERGE] Reference: https://github.com/networkupstools/nut/pull/473#39
geraldguillaume wants to merge 1 commit into42ity:FTYfrom
geraldguillaume:FTY

Conversation

@geraldguillaume
Copy link
Copy Markdown

fty-discovery needs and uses successfully this fix provided by @jimklimov, thanks to him.
This fix allow fty-discovery to do straightforward exec "/lib/nut/snmp-ups -s dumpdataXXX" and manage successfully timeout (signal SIGTERM/SIGKILL).

Signed-off-by: Gerald Guillaume geraldguillaume@eaton.com

Signed-off-by: Gerald Guillaume <geraldguillaume@eaton.com>
@jimklimov
Copy link
Copy Markdown
Member

That is an unconventional way of applying commits made (signed, dated) by others ;) Usually one adds the remote repo and cherry-picks stuff. When this lands into upstream and back to our fork, there will be less/no merge conflicts to solve.

Otherwise LGTM.

@aquette aquette changed the title Reference: https://github.com/networkupstools/nut/pull/473 [DO NOT MERGE] Reference: https://github.com/networkupstools/nut/pull/473 Nov 29, 2017
@aquette
Copy link
Copy Markdown
Member

aquette commented Nov 29, 2017

@jimklimov is right, even more considering the full-duplex synchro that needs to be done between upstream nut and fty version.
FYI, I'm preparing a complement to networkupstools#473 which adds the missing doc so that a complete PR can be merged upstream and reused here

@aquette
Copy link
Copy Markdown
Member

aquette commented Nov 29, 2017

Discarded by #40

@aquette aquette closed this Nov 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants