For example, if your server has only a character-based terminal as its console and you wish to run gr_osview(1M) to visually inspect your CPU usage, you would issue commands similar to these on the server:
When you invoke gr_osview, the window with the output will appear on the machine name you specify. In this example, graphics_machine was used in place of the system name. The :0 used after the machine name indicates that display monitor 0 (the graphics console) should be used to display the output. When you have finished using the graphics console, be sure to reset the display by issuing this command on the server:setenv DISPLAY graphics_machine:0
gr_osview
where local_server is the name of your server.setenv DISPLAY local_server:0
Processor 0: 40 MHZ IP7 Processor 1: 36 MHZ IP7 Processor 2: 40 MHZ IP7 Processor 3: 40 MHZ IP7 Processor 4: 40 MHZ IP7 Processor 5: 40 MHZ IP7 Processor 6: 40 MHZ IP7 Processor 7: 40 MHZ IP7Or, alternately, output similar to the following:
8 40 MHZ IP7 ProcessorsA single-processor system returns information similar to the following for the hinv command:
1 100 MHZ IP22 ProcessorIf you have only one processor on your system (and the vast majority of systems have only one processor) these commands still operate, though they have no useful purpose.
The mpadmin command allows you to ''turn off'' processors, report various states of the processors, and move system functions such as the system clock to specific processors. The pset command is used both to display and modify information concerning the use of processor sets and programs running in the current system. The pset command provides a much more detailed level of control of processes and processors.
For complete information on mpadmin(1M) and pset(1M), see the respective reference pages.
To display the name of the system, use the hostname command with no arguments:
This displays the name of the system. The uname command also displays the name of the system, along with other information.hostname
To change the name of the workstation, follow these steps:
For information about the Internet address of a workstation, see the IRIX networking documentation. For more information about the name of the system, see the hostname(1) and uname(1) reference pages.
To set the network address, follow these steps:
nvram netaddr 192.13.52.4
Note that the printer laser must already exist and be configured. For complete information on setting up printers, see the IRIX print services documentation.lpadmin -dlaser
The line# Time Zone
TZ=EST5EDT
TZ=EST5EDT
means:
Region | GMT Differential | Abbreviation |
---|---|---|
Newfoundland | -3:30 | NST |
Atlantic | -4:00 | AST |
Eastern | -5:00 | EST |
Central | -6:00 | CST |
Saskatchewan | -6:00 | CST |
Mountain | -7:00 | MST |
Pacific | -8:00 | PST |
Yukon | -9:00 | YST |
Alaska | -10:00 | AST |
Hawaii | -10:00 | HST |
Bering | -11:00 | BST |
BajaNorte | -8:00 | PST |
BajaSur | -7:00 | MST |
Mexico General | -6:00 | CST |
Region | GMT Differential | Abbreviation |
---|---|---|
Ireland | 0:00 | BST |
The United Kingdom | 0:00 | BST |
Western Europe | 0:00 | WET |
Iceland | 0:00 | WET |
Middle Europe | 1:00 | MET |
Poland | 1:00 | MET |
Eastern Europe | 2:00 | EET |
Turkey | 3:00 | EET |
Western Russia | 3:00 | WSU |
Region | GMT Differential | Abbreviation |
---|---|---|
Rep. Of China | 8:00 | CST |
Hongkong | 8:00 | HKT |
Japan | 9:00 | JST |
Rep. Of Korea | 9:00 | ROK |
Singapore | 8:00 | SST |
Region | GMT Differential | Abbreviation |
---|---|---|
Israel | 2:00 | IST |
Egypt | 2:00 | EET |
Region | GMT Differentia | Abbreviation |
---|---|---|
Brazil/East | -3:00 | EST |
Brazil/West | -4:00 | WST |
Brazil/Acre | -5:00 | AST |
Brazil/DeNoronha | -2:00 | FST |
Chile/Continental | -4:00 | CST |
Chile/EasterIsland | -6:00 | EST |
Region | GMT Differential | Abbreviation |
---|---|---|
Australia/Tasmania | 10:00 | EST |
Australia/Queensland | 10:00 | EST |
Australia/North | 9:30 | CST |
Australia/West | 8:00 | WST |
Australia/South | 9:30 | CST |
Australia/Victoria | 10:00 | EST |
Australia/NSW | 10:00 | EST |
New Zealand | 12:00 | NZT |
For complete information about setting your time zone, see the timezone(4) reference page.
Changing the date and time on a running system can have unexpected consequences. Users and administrators use system scheduling utilities (at(1), cron(1), and batch(1)) to perform commands at specified times. If you change the effective date or time on the system, these commands may not execute at the desired times. Similarly, if your users use the make(1) utility provided with the system, the commands specified in Makefiles can incorrectly compile or process your users' work. Always try to keep your system date and time accurate within reason. Random changes of the date and time can be extremely inconvenient and possibly destructive to users' work.date 0401090099
If timed(1M) is running on the system, and it is a slave system, the time is reset by timed and not the above command. For more information, see the timed(1M) reference page.