search for: atvups

Displaying 4 results from an estimated 4 matches for "atvups".

Did you mean: apcups
2014 Feb 07
2
BestPower Ferrups driver glitch with f commands
...r more lines starting with 'exec:' followed by an absolute path to the driver binary and some command line option. This is what the driver starts and you need to copy and paste that line and append the debug flags to that line (less the 'exec:' prefix). 0.000181 Starting UPS: ATVUPS 0.000194 exec: /usr/local/ups/bin/bestfcom -a ATVUPS -u root Network UPS Tools - Best Ferrups/Fortress driver 0.12 (2.7.1) Warning: This is an experimental driver. Some features may not function correctly. Unknown model id ? FERRUPS Uninterruptible Power System By Powerware Corporation 8609...
2014 Feb 08
0
BestPower Ferrups driver glitch with f commands
...th 'exec:' followed by an absolute > path to the driver binary and some command line option. This is what the driver > starts and you need to copy and paste that line and append the debug flags to that > line (less the 'exec:' prefix). > > 0.000181 Starting UPS: ATVUPS > 0.000194 exec: /usr/local/ups/bin/bestfcom -a ATVUPS -u root As the message suggests, for debugging the driver, you should bypass the upsdrvctl command (which really only helps when starting multiple drivers at once) and pass the -D flags directly to the driver: /usr/local/ups/bin/best...
2014 Feb 10
2
BestPower Ferrups driver glitch with f commands
...ith 'exec:' followed by an absolute > path to the driver binary and some command line option. This is what the driver > starts and you need to copy and paste that line and append the debug flags to that > line (less the 'exec:' prefix). > > 0.000181 Starting UPS: ATVUPS > 0.000194 exec: /usr/local/ups/bin/bestfcom -a ATVUPS -u root As the message suggests, for debugging the driver, you should bypass the upsdrvctl command (which really only helps when starting multiple drivers at once) and pass the -D flags directly to the driver: /usr/local/ups/bin/best...
2014 Feb 10
0
BestPower Ferrups driver glitch with f commands
...ith 'exec:' followed by an absolute > path to the driver binary and some command line option. This is what the driver > starts and you need to copy and paste that line and append the debug flags to that > line (less the 'exec:' prefix). > > 0.000181 Starting UPS: ATVUPS > 0.000194 exec: /usr/local/ups/bin/bestfcom -a ATVUPS -u root As the message suggests, for debugging the driver, you should bypass the upsdrvctl command (which really only helps when starting multiple drivers at once) and pass the -D flags directly to the driver: /usr/local/ups/bin/best...