1. Our global team of engineers and sales support staff can answer your toughest questions. We have offices located around the globe, so we understand challenges specific to your region and location. If you can't find the software downloads and drivers that you need here, please reach out to us for immediate assistance. We are glad to help.
2. The Canon PRINT app easily lets you print and scan photos or documents from your compatible mobile device. With the cloud print function, you can print directly from select online cloud services either at the printer itself or with your mobile device using the free PPS app. Gray ink helps produce professional-looking black & white and vibrant color photo prints.

Recommended to protect mission-critical equipment, Liebert® GXT4™ is a true on-line UPS that delivers continuous, high-quality AC power with no break when transferring to battery. It protects equipment from all power disturbances due to blackouts, brownouts, sags, surges or noise interference. Liebert GXT4 UPS.

nutupsdrv: generic manual for unified NUT drivers

Command to display nutupsdrv manual in Linux: $ man 8 nutupsdrv

NAME

nutupsdrv - generic manual for unified NUT drivers

SYNOPSIS

nutupsdrv-h

nutupsdrv [OPTIONS]

DESCRIPTION

nutupsdrv is not actually a driver. This is a combined man page for the shared code that is the core of many drivers within the Network UPS Tools package.

For information on the specific drivers, see their individual man pages.

UPS drivers provide a communication channel between the physical UPS hardware and the upsd(8) server. The driver is responsible for translating the native protocol of the UPS to the common format used by the rest of this package.

The core has two modes of operation which are determined by the command line switches. In the normal mode, the driver will periodically poll the UPS for its state and parameters. The results of this command is presented to upsd. The driver will also handle setting variables and instant commands if available.

The driver can also instruct the UPS to shut down the load, possibly after some delay. This mode of operation is intended for cases when it is known that the UPS is running out of battery power and the systems attached must be turned off to ensure a proper reboot when power returns.

You probably don't want to use any of these options directly. You should use upsdrvctl(8) to control your drivers, and ups.conf(5) to configure them. The rest of this manual describes options and parameters that generally are not needed by normal users.

OPTIONS

-h

-aid

-q

Raise log level threshold. Use this multiple times to log more details.

The debugging comment above also applies here.

-iinterval

Print only version information, then exit.

-L

You should useupsdrvctl shutdownwhenever possible instead of calling this directly.

-rdirectory

The driver will chroot(2) todirectoryduring initialization. This can be useful when securing systems.

In addition to the state path, many systems will require /dev/null to exist withindirectoryfor this to work. The serial ports are opened before the chroot call, so you do not need to create them inside the jail. In fact, it is somewhat safer if you do not.

-uusername

If started as root, the driver will setuid(2) to the user id associated withusername.

If you do not specify this value and start it as root, the driver will switch to the default value that was compiled into the code. This is typicallynobody, and is far from ideal.

-xvar=val

Define a variable calledvarwith the value ofvarin the driver. This varies from driver to driver - see the specific man pages for more information.

This is like settingvar=valinups.conf(5), but-xoverrides any settings from that file.

DIAGNOSTICS

Information about the startup process is printed to stdout. Additional messages after that point are available in the syslog. After upsd(8) starts, the UPS clients such as upsc(8) can be used to query the status of an UPS.

PROGRAM CONTROL

You should always use upsdrvctl(8) to control the drivers. While drivers can be started by hand for testing purposes, it is not recommended for production use.

FILES

ups.conf

nutupsdrv-h

nutupsdrv [OPTIONS]

DESCRIPTION

nutupsdrv is not actually a driver. This is a combined man page for the shared code that is the core of many drivers within the Network UPS Tools package.

For information on the specific drivers, see their individual man pages.

UPS drivers provide a communication channel between the physical UPS hardware and the upsd(8) server. The driver is responsible for translating the native protocol of the UPS to the common format used by the rest of this package.

The core has two modes of operation which are determined by the command line switches. In the normal mode, the driver will periodically poll the UPS for its state and parameters. The results of this command is presented to upsd. The driver will also handle setting variables and instant commands if available.

The driver can also instruct the UPS to shut down the load, possibly after some delay. This mode of operation is intended for cases when it is known that the UPS is running out of battery power and the systems attached must be turned off to ensure a proper reboot when power returns.

Note

You probably don't want to use any of these options directly. You should use upsdrvctl(8) to control your drivers, and ups.conf(5) to configure them. The rest of this manual describes options and parameters that generally are not needed by normal users.

OPTIONS

-h

-aid

-D

Raise the debugging level. Use this multiple times to see more details. Running a driver in debug mode will prevent it from backgrounding after startup. It will keep on logging information to the console until it receives a SIGINT (usually Ctrl-C) or SIGTERM signal.

The level of debugging needed depends both on the driver and the problem you're trying to diagnose. Therefore, first explain the problem you have with a driver to a developer/maintainer, before sending them debugging output. More often than not, if you just pick a level, the output may be either too limited or too verbose to be of any use.

-q

Raise log level threshold. Use this multiple times to log more details.

The debugging comment above also applies here.

-iinterval

Print only version information, then exit.

-L

You should useupsdrvctl shutdownwhenever possible instead of calling this directly.

-rdirectory

The driver will chroot(2) todirectoryduring initialization. This can be useful when securing systems.

In addition to the state path, many systems will require /dev/null to exist withindirectoryfor this to work. The serial ports are opened before the chroot call, so you do not need to create them inside the jail. In fact, it is somewhat safer if you do not.

-uusername

If started as root, the driver will setuid(2) to the user id associated withusername.

Drivers Liebert Wireless

If you do not specify this value and start it as root, the driver will switch to the default value that was compiled into the code. This is typicallynobody, and is far from ideal.

-xvar=val

Define a variable calledvarwith the value ofvarin the driver. This varies from driver to driver - see the specific man pages for more information.

This is like settingvar=valinups.conf(5), but-xoverrides any settings from that file.

DIAGNOSTICS

Information about the startup process is printed to stdout. Additional messages after that point are available in the syslog. After upsd(8) starts, the UPS clients such as upsc(8) can be used to query the status of an UPS.

PROGRAM CONTROL

You should always use upsdrvctl(8) to control the drivers. While drivers can be started by hand for testing purposes, it is not recommended for production use.

FILES

ups.conf