• Last 5 Forum Topics
    Last post

The Web Only This Site



  • MARC

    Mailing list ARChives
    - Search by -


    Computing Dictionary

  • Text Link Ads

  • LINUX man pages
  • Linux Man Page Viewer

    The following form allows you to view linux man pages.





           This man page only documents the hardware-specific features of the
           belkin driver. For information about the core driver, see nutupsdrv(8).


           The belkinunv driver is known to work with the Belkin Universal UPS
           models F6C800-UNV and F6C120-UNV, and is expected to work with other
           Belkin Universal UPS models. The driver only supports serial
           communication, not USB.
           The Trust UPS and older Belkin units are not supported by this driver,
           and neither are the Belkin Home Office models (F6H500-SER and so
           forth). However, some Belkin models, such as the Regulator Pro, are
           supported by the belkin(8) driver, and the Home Office models are
           supported using the genericups(8) driver with upstype=7.


           One problem with the Belkin Universal UPS is that it cannot enter a
           soft shutdown (shut down the load until AC power returns) unless the
           batteries are completely depleted. Thus, one cannot just shut off the
           UPS after operating system shutdown; it will not come back on when the
           power comes back on. Therefore, the belkinunv driver should never be
           used with the -k option. Instead, the -x wait option is provided as a
           When called with the -x wait option, belkinunv behaves as a standalone
           program (i.e., it does not fork into the background). It performs one
           simple task: it connects to the UPS, waits for AC power to return, and
           then exits with status 0.
           This is meant to be used in a shutdown script as follows: during a
           shutdown, after all filesystems have been remounted read-only, and just
           before the system would normally be halted: check /etc/killpower (or
           similar) to see if this shutdown was caused by upsmon(8), and if yes,
           call belkinunv -x wait. If AC power comes back on, belkinunv exits, and
           things should be arranged so that the system reboots in this case. If
           AC power does not come back on, the UPS will eventually run out of
           batteries, kill the computer's power supply, and go into soft shutdown
           mode, which means everything will reboot properly when the power
           returns. In either case, a deadlock is avoided.
           In addition, if an optional integer argument is given to the -x wait
           option, this causes belkinunv to wait not only for AC power to be
           present, but also for the battery charge to reach the given level. I
           use this as part of my startup scripts, to ensure that the batteries
           are sufficiently charged before the computer continues booting. This
           should be put very early in the startup script, before any filesystems
           are mounted read/write, and before any filesystem checks are performed.
           Several other -x options are provided to fine-tune this behavior. See
           the options below for detailed descriptions. See the examples below for
           examples of how to use belkinunv in shutdown and startup scripts.
               described under Soft Shutdown Workaround above.
           -x nohang
               This option only has an effect when used in conjunction with the -x
               wait option. It causes belkinunv to exit if a connection with the
               UPS cannot be established or is lost, instead of retrying forever,
               which is the default behavior. The -x nohang option should be used
               in a startup script, to ensure the computer remains bootable even
               if the UPS has been disconnected during the power failure (for
               instance, you attached your computer to a generator, carried it to
               a neighbor's house, or whatever).
           -x flash
               This option only has an effect when used in conjunction with the -x
               wait option. It causes the UPS load to be shut off for a short time
               ("flashed") just after the AC power has returned and the requested
               battery level (if any) has been attained. This is useful if slaves
               are attached to this UPS; the flash will cause all of them to
               reboot. Note that, due to the design of the Belkin UPS hardware,
               the load shutdown lasts ca. 1--2 minutes; a shorter flash cannot be
               performed reliably. Also, the computers will reboot at the
               scheduled time, on battery power if necessary, even if AC power
               fails again in the meantime. This should not be a problem, as your
               startup scripts can catch this situation.
           -x silent
               This option only has an effect when used in conjunction with the -x
               wait option. It suppresses the status line which belkinunv would
               normally print.
           -x dumbterm
               This option only has an effect when used in conjunction with the -x
               wait option. It changes the way in which belkinunv prints its
               status line. Normally, terminal control sequences are used to
               overwrite the same line with new status information, each time the
               status is updated. This may not work on all terminals. If the -x
               dumbterm option is given, each status update is written on a new


           battery.charge, battery.runtime
               not supported by all hardware.
           battery.voltage, battery.voltage.nominal, driver.version.internal,
           input.frequency, input.frequency.nominal
               e.g. 60 for 60Hz
               writable: normal/medium/low
               writable: high transfer voltage point in V
               battery). Note that not all UPS models support the "disabled"
           ups.firmware, ups.load, ups.model, ups.power.nominal
               e.g. 800 for an 800VA system
               a list of flags; see the status flags below.
               not supported by all hardware.
           ups.test.result, ups.delay.restart
               time to restart (read only)
               time to shutdown (read only). This is always a multiple of 60
               ONLINE/OFFLINE/LINEINT. This describes the basic layout of this UPS
               (for GUI clients which want to draw an animated picture of power
               flow). An offline UPS has a direct connection from AC input to AC
               output, and also a connection from AC input to the battery, and
               from the battery to AC output. An online UPS lacks the direct
               connection from AC input to AC output, whereas a line interactive
               UPS lacks the connection from AC input to the battery.


           beeper.enable, beeper.disable, beeper.mute
               Enable, disable or mute the panel beeper. Note that if the beeper
               is muted, it is automatically turned back on at the next event (AC
               failure, battery test, etc). Also, the beeper can't be turned muted
               during a critical event (low battery).
               Reset the variables input.voltage.minimum and
               Shut down load immediately for about 1--2 minutes.
               After 40 second delay, shut down load for about 1--2 minutes.
               Shut down load immediately and stay off. The only way it can be
               turned back on is by manually pressing the front panel button.
           test.battery.start, test.battery.stop
               Start/stop 10 second battery test.
               AC failure. Note that this refers to the AC input, and thus it is
               not the same as "OB". An AC failure can occur at any time, for
               instance, during a battery test, or when the UPS load is off.
               UPS fault
               low battery
               the battery is depleted. When the UPS raises this flag, it
               simultaneously switches off the load.
               replace battery


           Here is an example for how belkinunv should be used in a computer's
           shutdown script. These commands should go in the very last part of the
           shutdown script, after all file systems have been mounted read-only,
           and just before the computer halts. Note that belkinunv must be
           installed in a directory which is still readable at that point.
               # if shutdown was caused by UPS, perform Belkin UPS workaround.
               if [ -f /etc/killpower ] ; then
                  echo "Waiting for AC power, or for UPS batteries to run out..."
                  /usr/bin/belkinunv -x wait /dev/ttyS1
                  # we get here if the power came back on. Reboot.
                  echo "Power is back. Rebooting..."
           And here is an example of how to use belkinunv in the startup script.
           These commands should go near the beginning of the startup script,
           before any file systems are mounted read/write, and before any file
           system integrity checks are done.
               # if we are recovering from a power failure, wait for the UPS to
               # charge to a comfortable level before writing anything to disk


           This driver does not support any extra settings in ups.conf(5).


       The core driver:
       Internet resources:
           ?   The NUT (Network UPS Tools) home page:
           ?   The documentation for the protocol used by this UPS:


           Peter Selinger <>

    Network UPS Tools 10/09/2011 BELKINUNV(8)


  • Linux

    The Distributions


    The Software


    The News


  • Toll Free
Copyright © 1999 - 2016 by LinuxGuruz