Hi Charles; I had nut working from before, but managed to lock up something and had to reboot. Nut is in the stuff to start at boot time, but is not now capable to being restarted with the nut script in /etc/init.d, claiming it is disabled: gene at coyote:/usr/src/nut-2.7.2/docs/man$ sudo service nut start * nut disabled, please adjust the configuration to your needs * Then set MODE to a suitable value in /usr/local/ups/etc/nut/nut.conf to enable it gene at coyote:/usr/src/nut-2.7.2/docs/man$ service nut start * nut disabled, please adjust the configuration to your needs * Then set MODE to a suitable value in /usr/local/ups/etc/nut/nut.conf to enable it So I look at that file and see it has only one active line: mode=standalone So where do I go from here? Minor rant: FWIW, before I asked, I redid the nut ./configure --with-doc=auto, then a make. Then I step into the docs directory and do a sudo make install, which it appears to do. But no manpages were install despite the command line echo showing that they were when I did the sudo make install, but I am forced to go into the docs directory and a man ./name-of-man-page to read it, and mode is only mentioned briefly in the example line which shows mode=none. That is a 10-33 torr suckage. This I think can be alleviated by setting up the env variable MANPATH, which is not apparently configured. Export that and it works. So put it in my .bashrc But since every other manpage on the system works without that env setting of $MANPATH, showing "/usr/local/ups/share/man:/usr/share/man" when queried now, why should i have to do it for nuts man pages? Boggles the mind. End minor rant. And I still cannot start it, see above. The error msg says its disabled, but not why, so I've exactly no clue what is really wrong. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS
Charles Lepple
2014-Dec-02 01:35 UTC
[Nut-upsuser] puzzle, need magic incantation (nut.conf)
On Dec 1, 2014, at 9:43 AM, Gene Heskett <gheskett at wdtv.com> wrote:> Hi Charles; > > I had nut working from before, but managed to lock up something and had to > reboot. Nut is in the stuff to start at boot time, but is not now capable > to being restarted with the nut script in /etc/init.d, claiming it is > disabled: > > gene at coyote:/usr/src/nut-2.7.2/docs/man$ sudo service nut start > * nut disabled, please adjust the configuration to your needs > * Then set MODE to a suitable value in /usr/local/ups/etc/nut/nut.conf to > enable it > gene at coyote:/usr/src/nut-2.7.2/docs/man$ service nut start > * nut disabled, please adjust the configuration to your needs > * Then set MODE to a suitable value in /usr/local/ups/etc/nut/nut.conf to > enable it > > So I look at that file and see it has only one active line: > mode=standaloneHi Gene, Is the "MODE" token capitalized? (The nut.conf file is included in the startup shell script, which is case-sensitive.) Here is the original nut.conf with its comments: https://github.com/networkupstools/nut/blob/587d5f828c03d961f0cbeb11c6a19a7944ec6ccd/conf/nut.conf.sample -- Charles Lepple clepple at gmail
Charles Lepple
2014-Dec-02 01:43 UTC
[Nut-upsuser] puzzle, need magic incantation (man pages)
On Dec 1, 2014, at 9:43 AM, Gene Heskett <gheskett at wdtv.com> wrote:> FWIW, before I asked, I redid the nut ./configure --with-doc=auto, then a > make. Then I step into the docs directory and do a sudo make install, > which it appears to do. But no manpages were install despite the command > line echo showing that they were when I did the sudo make install, but I > am forced to go into the docs directory and a man ./name-of-man-page to > read it, and mode is only mentioned briefly in the example line which > shows mode=none. That is a 10-33 torr suckage.I think that other link I sent to the sample nut.conf has all of the possible values there - not sure what happened to those comments in your original file.> This I think can be alleviated by setting up the env variable MANPATH, > which is not apparently configured. Export that and it works. So put it > in my .bashrc > > But since every other manpage on the system works without that env setting > of $MANPATH, showing "/usr/local/ups/share/man:/usr/share/man" when > queried now, why should i have to do it for nuts man pages? Boggles the > mind.If you run "./configure" without passing, say, "--prefix=/usr/local", it will default to "--prefix=/usr/local/ups" which has the advantage of putting everything in one directory. To clean up, you just delete /usr/local/ups. Cleaning up after a botched install to /usr/local is painful, either involving backups, or surgically removing files from bin/, sbin/, etc/, man/man?/, etc. -- Charles Lepple clepple at gmail
Gene Heskett
2014-Dec-02 05:07 UTC
[Nut-upsuser] puzzle, need magic incantation (nut.conf)
On Monday 01 December 2014 20:35:15 Charles Lepple did opine And Gene did reply:> On Dec 1, 2014, at 9:43 AM, Gene Heskett <gheskett at wdtv.com> wrote: > > Hi Charles; > > > > I had nut working from before, but managed to lock up something and > > had to reboot. Nut is in the stuff to start at boot time, but is > > not now capable to being restarted with the nut script in > > /etc/init.d, claiming it is disabled: > > > > gene at coyote:/usr/src/nut-2.7.2/docs/man$ sudo service nut start > > * nut disabled, please adjust the configuration to your needs > > * Then set MODE to a suitable value in > > /usr/local/ups/etc/nut/nut.conf to enable it > > gene at coyote:/usr/src/nut-2.7.2/docs/man$ service nut start > > * nut disabled, please adjust the configuration to your needs > > * Then set MODE to a suitable value in > > /usr/local/ups/etc/nut/nut.conf to enable it > > > > So I look at that file and see it has only one active line: > > mode=standalone > > Hi Gene, > > Is the "MODE" token capitalized?Yes. The one in /usr/local/ups/etc is the only one it can find Copy/paste: MODE=standalone Aha! The paths in the /etc/init.d/nut script were wrong. Fixed that up and a sudo service nut restart seems to have fired it right up. Except that /usr/local/ups/bin/upsc myups is connection refused. And it is not visible in htop. Next? Thank you Charles> (The nut.conf file is included in the startup shell script, which is > case-sensitive.) > > Here is the original nut.conf with its comments: > > https://github.com/networkupstools/nut/blob/587d5f828c03d961f0cbeb11c6a > 19a7944ec6ccd/conf/nut.conf.sampleCheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS
Gene Heskett
2014-Dec-02 05:09 UTC
[Nut-upsuser] puzzle, need magic incantation (man pages)
On Monday 01 December 2014 20:43:37 Charles Lepple did opine And Gene did reply:> On Dec 1, 2014, at 9:43 AM, Gene Heskett <gheskett at wdtv.com> wrote: > > FWIW, before I asked, I redid the nut ./configure --with-doc=auto, > > then a make. Then I step into the docs directory and do a sudo make > > install, which it appears to do. But no manpages were install > > despite the command line echo showing that they were when I did the > > sudo make install, but I am forced to go into the docs directory and > > a man ./name-of-man-page to read it, and mode is only mentioned > > briefly in the example line which shows mode=none. That is a 10-33 > > torr suckage. > > I think that other link I sent to the sample nut.conf has all of the > possible values there - not sure what happened to those comments in > your original file. > > > This I think can be alleviated by setting up the env variable > > MANPATH, which is not apparently configured. Export that and it > > works. So put it in my .bashrc > > > > But since every other manpage on the system works without that env > > setting of $MANPATH, showing > > "/usr/local/ups/share/man:/usr/share/man" when queried now, why > > should i have to do it for nuts man pages? Boggles the mind. > > If you run "./configure" without passing, say, "--prefix=/usr/local", > it will default to "--prefix=/usr/local/ups" which has the advantage > of putting everything in one directory. To clean up, you just delete > /usr/local/ups. Cleaning up after a botched install to /usr/local is > painful, either involving backups, or surgically removing files from > bin/, sbin/, etc/, man/man?/, etc.BTDT, not fun. Thanks Charles Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS