On 03/22/2018 07:43 PM, Charles Lepple wrote:
If the Slackware startup scripts call "upsdrvctl start", and the UPS
is listed in ups.conf, that should start the driver at boot.
Now I see that also after doing necessary things in
http://networkupstools.org/docs/user-manual.chunked/index.html
On Mar 22, 2018, at 10:22 PM, David Melik wrote:
>
> I assume if I just go through the setup instructions on the NUT website,
> that'll make the server automatically load this driver on boot.
If the Slackware startup scripts call "upsdrvctl start", and the UPS is listed
in
On 03/21/2018 07:07 PM, Charles Lepple wrote:
On Mar 20, 2018, at 6:06 PM, David Melik wrote:
Ok, around 24hrs ago I retested, but the (same) output is still on
the screen without it going into background to release tty/sh...
My mistake - I misinterpreted the log you posted. Without the "-D"
On Mar 20, 2018, at 6:06 PM, David Melik wrote:
>
> On 03/19/2018 04:49 AM, Charles Lepple wrote:
>> The rc-style init systems typically want programs like the drivers to go
>> into the background on their own (as the driver does without "-D", or when
>> launched by "upsdrvctl start"). Other
On 03/19/2018 04:49 AM, Charles Lepple wrote:
The rc-style init systems typically want programs like the drivers to
go into the background on their own (as the driver does without "-D",
or when launched by "upsdrvctl start"). Other init systems like
launchd or systemd will monitor the PID of
On Mar 19, 2018, at 4:00 AM, David Melik wrote:
>
>> Then you can launch the driver with at least one "-D" flag:
>>
>> /usr/libexec/nut/bestfcom -a ups -D
>
> I thought there was a lot more to it than that, but after I ran that stuff,
> the driver outputs. However, /etc/rc.d/rc.ups
On 02/20/2018 06:16 PM, Charles Lepple wrote:
Do you have a pinout for that cable?
Unsure, but after recent suggestions, it may be working. Already had
NUT from SlackBuilds.org (SBo) installed, but reinstalled to add the
group:user.
I forget if it is the default, but you might need to
On Feb 19, 2018, at 3:44 PM, David Melik wrote:
>
> Minicom listed a blank modem init string, and 'f' did nothing.
Do you have a pinout for that cable?
I forget if it is the default, but you might need to turn off the hardware and
software flow control (minicom: Ctrl-A then letter O, "Serial
On 02/13/2018 03:49 AM, Charles Lepple wrote:
On Feb 12, 2018, at 11:53 PM, David Melik wrote:
On 01/21/2018 05:53 AM, Charles Lepple wrote:
If you hook up a terminal emulator to the comms port (1200 baud, 8/N/1 unless stickers and/or
configuration DIP switches indicate otherwise), and type
On 02/12/2018 11:53 PM, David Melik wrote:
>
> Of course, I got Eaton Powerware's RS-232 cable for FE700VA/etc. but
> don't know what 'hook up a terminal emulator'... no Slackware
> GNU/Linux BASH command 'f,' or do I run (or install/compile) a certain
> program to enable/access that?
The classic
On Feb 12, 2018, at 11:53 PM, David Melik wrote:
>
> On 01/21/2018 05:53 AM, Charles Lepple wrote:
>> If you hook up a terminal emulator to the comms port (1200 baud, 8/N/1
>> unless stickers and/or configuration DIP switches indicate otherwise), and
>> type "f" , do you get a status line like
On 01/21/2018 05:53 AM, Charles Lepple wrote:
My understanding was that many of the older Best Power units were downstream of
generators, and as such, full-blown power outages of both mains and generator
power were not expected.
That said, it might be that the "bestfcom" driver predates when
On Jan 21, 2018, at 1:12 AM, David Melik wrote:
>
> I have an excellent old Best Power FE700VA but am suprised it's unlisted. I
> thought Best Power ones were for critical applications, mostly for
> POSIX-based (Unix, etc.) servers, so I want to run it on 64-bit Slackware
I have an excellent old Best Power FE700VA but am suprised it's
unlisted. I thought Best Power ones were for critical applications,
mostly for POSIX-based (Unix, etc.) servers, so I want to run it on
64-bit Slackware GNU/Linux. I'm wondering why, or if it may be added in
the future, or if
14 matches
Mail list logo