Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (HP-UX-11.11)
Apropos / Subsearch:
optional field

 @(#)  power_onoff.1m  $Date:  2001/09/25   17:51:18   $Revision:   r11.11/2
 PATCH_11.11 (PHCO_24173)

				    - 1 -	  Formatted:  August 2, 2006

 power_onoff(1M)					     power_onoff(1M)

      power_onoff - timed, automatic system power on, and power off

      /usr/sbin/power_onoff -n

      /usr/sbin/power_onoff time  [date] [[next | +increment]

      power_onoff instructs the UPS monitor (ups_mond) to shut down the
      system, and optionally informs the monitor when to power on the system
      again.  The UPS monitor in turn instructs the uninterruptible power
      source (UPS) when to turn the power off and on.  The UPS monitor then
      proceeds to shut down the system.	 The time to restart the system
      (power on) is specified with power_onoff command-line arguments.

      Some UPS units limit the time that can elapse between the time the
      power is turned off and the time it is turned back on.  Please see
      your UPS documentation for information about limitations.

      power_onoff requires a UPS that is supported by the UPS monitor (see

    Command Line Arguments
      The power_onoff command has two forms, and recognizes the following

      -n	  No power on.	Causes the system to be shutdown and not be
		  powered back on.

      time	  Can be specified as one, two, or four digits.	 One- and
		  two-digit numbers represent hours; four digits represent
		  hours and minutes.  time can also be specified as two
		  numbers separated by a colon (:), single quote ('), the
		  letter "h" (h), a period (.), or comma (,).  A suffix am
		  or pm can be appended.  Otherwise a 24-hour clock time is
		  understood.  For example, 0815, 8:15, 8'15, 8h15, 8.15,
		  and 8,15 are read as 15 minutes after 8 in the morning.
		  The suffixes zulu and utc can be used to indicate
		  Coordinated Universal Time.  The special names noon,
		  midnight, now, and next are also recognized.

      date	  Can be specified as either a day of the week (fully
		  spelled out or abbreviated) or a date consisting of a day,
		  a month, and optionally a year.  The day and year fields
		  must be numeric, and the month can be fully spelled out,
		  abbreviated, or numeric.  These three fields can be in any
		  order, and be separated by punctuation marks such as slash
		  (/), hyphen (-), period (.), or comma (,).  The years 00-
		  68 would be interpreted as 2000-2068 and 69-99 would be

				    - 1 -	  Formatted:  August 2, 2006

 power_onoff(1M)					     power_onoff(1M)

		  1969-1999.  Two special ``days'', today and tomorrow, are
		  also recognized.  If no date is given, today is assumed if
		  the given time is greater than the current time; tomorrow
		  is assumed if it is less.  If the given month is less than
		  the current month (and no year is given), next year is

      next	  If followed by a time_designation of minutes, hours, days,
      or	  weeks, months, or years, lets the user startup the system
      +increment  when the specified time_designation has elapsed.  A
		  numerical operator, +increment, enables the user to
		  schedule the startup several hours, days, weeks, months,
		  or years in advance (see EXAMPLES).  Using the argument
		  next is equivalent to using an increment of +1.  Both
		  plural and singular forms of time_designation are

    International Code Set Support
      Single- and multi-byte character code sets are supported.

      Exit code 0 is returned upon successful completion, otherwise non 0 is

      power_onoff issues diagnostic messages when it encounters syntax
      errors and out-of-range times.

      To startup the system at 5:00 am next Tuesday, use

	   power_onoff 5am Tuesday next week

      To startup the system at 5:30 am tomorrow, use

	   power_onoff 5:30 tomorrow

      To make your system startup each weekday at 7:30 am and shutdown at
      5:30 pm each week day, use crontab to execute the first entry on
      Monday through Thursday and the second entry on Friday (see

	   power_onoff 7:30 tomorrow

	   power_onoff 7:30 Monday

      To startup the system at 8:15 on January 24, use

	   power_onoff 0815 Jan 24

				    - 2 -	  Formatted:  August 2, 2006

 power_onoff(1M)					     power_onoff(1M)

      To startup the system at 5:15 on January 24, use

	   power_onoff 5:15 Jan 24

      To startup the system at 9:30 tomorrow, use

	   power_onoff 9:30am tomorrow

      To startup the system 24 hours from now, use

	   power_onoff now + 1 day

      To shutdown the system and not start it up, use

	   power_onoff -n

      Jobs can be submitted up to 2037. If jobs were submitted any later
      than 2037, an error message will display "BAD DATE".

      Some UPS units limit the time that can elapse between the time the
      power is turned off and the time it is turned back on.  Please see
      your UPS documentation for information about limitations.

      If the date argument begins with a number and the time argument is
      also numeric (and without suffix), the time argument should be a
      four-digit number that can be correctly interpreted as hours and

      Do not use both next and + increment within a single power_onoff
      command; only the first operator is accepted and the trailing operator
      is ignored.  No warning or error is produced.

      The power cord must be disconnected before servicing the unit.

      power_onoff was developed by HP.

      /var/tmp/timed_off		 fifo for communicating with

      at(1), cron(1M), crontab(1), queuedefs(4), proto(4), kill(1), sam(1M),

				    - 3 -	  Formatted:  August 2, 2006