On Sep 10, 2014, at 9:18 AM, Rob Groner <rgroner at RTD.com> wrote:>> >>> 2) The "Starting the driver" section says to start the driver at >>> /usr/local/ups/sbin/upsdrvctl , but it's actually located at >>> /usr/lib/ups/driver/ >> >> Right, that was fixed post-2.6 (note that the web pages are all tagged with >> the version they correspond to; currently 2.7.2) > > I can't see on the webpages where it refers to being about version 2.7.2. Is this tagging in the html itself?My fault, the version is only included in the website pages, e.g. http://www.networkupstools.org/documentation.html https://github.com/networkupstools/nut/issues/150>>> 3) Under Installation Instructions, under "State path creation", it >>> says to create the directories and make them owned by the user you >>> created. It shows "chown root:nut /var/state/ups", but shouldn't it >>> be "chown ups:nut /var/state/ups" (I know any user/group can be used, >>> but ups:nut is what the example had been using so far). >> >> Assuming this is true: >> >>>> Be sure the new user is a member of the new group! If you forget to >>>> do this, you will have problems later on when you try to start upsd. >> >> and the mode is 0770, then the NUT user can access those directories, and >> change the contents, but cannot change the directory itself. > > Ok, that makes sense, but then maybe the wording should be "owned by the group" instead of "user"? Then there wouldn't be confusion between what it says to do and the command to do it.Makes sense. Also added to the TODO list: https://github.com/networkupstools/nut/issues/151>>> Just thought I would mention them. If those paths are distro/package >>> dependent, then that is ok, but it'd be nice of the docs said that. I >>> know elsewhere they do (when talking about installing from source). >> >> Seems like a good idea in principle. How would you reword it? > > Well, since the paths really become important when dealing with the configuration, perhaps at the top of page 6, under the "Note" already there, it could just be said that the paths to the configuration files are distribution dependent, and the ones shown are for <insert distro used here>. That way, whether someone's coming from the package install or source install, they would both end up at the top of that page and get the note before they start seeing the specific paths.When you say "Page 6", are you referring to a PDF? Or a sub-section in "Configuration"? -- Charles Lepple clepple at gmail
> >>> 2) The "Starting the driver" section says to start the driver at > >>> /usr/local/ups/sbin/upsdrvctl , but it's actually located at > >>> /usr/lib/ups/driver/ > >> > >> Right, that was fixed post-2.6 (note that the web pages are all > >> tagged with the version they correspond to; currently 2.7.2) > > > > I can't see on the webpages where it refers to being about version 2.7.2. Is > this tagging in the html itself? > > My fault, the version is only included in the website pages, e.g. > http://www.networkupstools.org/documentation.html > > https://github.com/networkupstools/nut/issues/150 > > >>> 3) Under Installation Instructions, under "State path creation", it > >>> says to create the directories and make them owned by the user you > >>> created. It shows "chown root:nut /var/state/ups", but shouldn't it > >>> be "chown ups:nut /var/state/ups" (I know any user/group can be > >>> used, but ups:nut is what the example had been using so far). > >> > >> Assuming this is true: > >> > >>>> Be sure the new user is a member of the new group! If you forget > >>>> to do this, you will have problems later on when you try to start upsd. > >> > >> and the mode is 0770, then the NUT user can access those directories, > >> and change the contents, but cannot change the directory itself. > > > > Ok, that makes sense, but then maybe the wording should be "owned by > the group" instead of "user"? Then there wouldn't be confusion between > what it says to do and the command to do it. > > Makes sense. Also added to the TODO list: > https://github.com/networkupstools/nut/issues/151 > > >>> Just thought I would mention them. If those paths are > >>> distro/package dependent, then that is ok, but it'd be nice of the > >>> docs said that. I know elsewhere they do (when talking about installing > from source). > >> > >> Seems like a good idea in principle. How would you reword it? > > > > Well, since the paths really become important when dealing with the > configuration, perhaps at the top of page 6, under the "Note" already there, > it could just be said that the paths to the configuration files are distribution > dependent, and the ones shown are for <insert distro used here>. That way, > whether someone's coming from the package install or source install, they > would both end up at the top of that page and get the note before they start > seeing the specific paths. > > When you say "Page 6", are you referring to a PDF? Or a sub-section in > "Configuration"?Sorry... The web pages, where you're sent when you click the "NUT Configuration" link. "6. Configuration Notes" (ar01s06.html)> Charles Lepple > clepple at gmail > >