<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div><span style="background-image:;background-position-x:;background-position-y:;background-size:;background-repeat-x:;background-repeat-y:;background-attachment:;background-origin:;background-clip:;background-color:;color:var(--pageTextColor);">On Fri, Mar 12, 2021, at 6:52 PM, Jim Klimov via Nut-upsuser wrote:</span><br></div><blockquote type="cite" id="qt" style=""><div dir="auto"><div>Hello fellow NUTs :)<br></div><div dir="auto"><br></div><div dir="auto"> Some time ago an issue <a href="https://github.com/networkupstools/nut/issues/840">https://github.com/networkupstools/nut/issues/840</a> was raised, and with current work underway to publish a standard on NUT protocol it became more urgent - to retire the master/slave terminology from NUT configuration and documentation.<br></div><div dir="auto"><br></div><div dir="auto"> I looked around for suitable synonyms, and for our primary use-case with upsmon roles - where it either manages an UPS by direct link and tells others to shut down ASAP, or is one of such shutdown agents being told what to do, words "manager" and "subordinate" seem neutral enough and reflective of the activities and relationship of these actors.<br></div><div dir="auto"><br></div><div dir="auto"> Would native speakers or others better versed in the current dictionary of acceptable words please confirm if this choice is okay, or suggest better alternatives?<br></div></div></blockquote><div><br></div><div>What about primary and secondary?<br></div><div id="sig65064480"><div class="signature">--<br></div><div class="signature"> Dan Langille<br></div><div class="signature"> dan@langille.org<br></div><div class="signature"><br></div></div><div><br></div></body></html>