Maintenance Commands                                WOOM/BOOM(1M)



NAME

woom/boom - Boot and Workstation Administration and Instal- lation

SYNOPSIS

woom/boom [-list] [-numbers] [-view] [-check] [-compare] [-new] [-change] [-install] [-apply PRODUCT][-push PRODUCT] [-from REPOSITORY] [-operating] [-disable] [-silent][-s] [-verbose][-v] [-default][-d] [-noaction][-n] [-preference][-p] {list|boot|merge} [-cfile OOMCONF] [-nolock] [-dns] [-offline] [-secure] [-german] [-import FILE] [-as REFDEV] [-doom {DB|all|default}] [-find PATTERN ... ] [-ignore PATTERN ... ] [-FIELDNAME value ... ] [-ARRAYNAME +value ... ] [-ARRAYNAME -value ... ] [-to TARGET | -target_object TARGET ] [ {devicename(s)|pattern(s)} ... ]

DESCRIPTION

Programs woom and boom or the german versions gwoom and gboom are for administration of administrative or technical data of devices like workstations, xterminals, PC's, printer, ... . Woom(WOrkstatiOn Management) and boom(BOOt Management) differ in the selection of the technical data items. Workstations may have multiple network interfaces with individual configuration and routing while boot devices normally have only one network interface with standard con- figuration and an optional alias name. The postprocessing of this data for later automatic installation takes care of that different behaviour. SunOS 5.10 Last change: 1 Maintenance Commands WOOM/BOOM(1M) A special case are PC's. Those are either administered by woom or boom dependent on e.g. the number of network inter- faces or the expected funktionality as workgroupserver or desktop device. The description is under preparation. Use the help option instead. Information on data field options should always be retrieved from the help function or the www information because these are under dynamic configuration.

VERSION

Version of this file @(#)wboom.1 1.16

OPTIONS

-german Provide german messages. This is the default if you call woom as gwoom or boom as gboom -silent | -s Do less output. -verbose | -v Provide more verbose information on output. If you prepend this option to the help option additional information on menus and choices appear. -noaction | -n This option selects a noaction mode during installa- tions. It it planned to extend this also to data operations. -help | -h Print the actual option list. Optionally start a WEB browser on available documentation if the DISPLAY vari- able is set. -dns This option sets the default answer to yes in case of necesary DNS operations. -offline This option inhibits remote accesses to the actual tar- gets. This may be helpfull in case of new devices or if you prefere viewing of postprocessing data instead of device data. -secure Change from remote shell protocol (rsh/remsh) to secure shell protocol (ssh). -operating This option starts a special operation mode with SunOS 5.10 Last change: 2 Maintenance Commands WOOM/BOOM(1M) defaults providing an easy interface to applying ser- vice operations to machines. -cfile OOMCONF There is a default configuration path /usr/local/etc/oom.conf. You can add additional confi- guration by applying this option. -list | -numbers These are listing and statistic functions. Without using the -item FIELDNAME option device names or numbers are provided. By specifying -item FIELDNAME options the selected fields are shown or analysed. -view | -check | -compare These options show device data. The check function has two columns and shows additionally to the list function device, postprocessing or import data. The compare function must be used together with the -as DEFREF option to show two devices in two columns. -new | -change These functions may change device data. The change function differs from the new function in that way that always even for filled fields questions for changes are asked. -install | -apply PRODUCT | -push These options provide installation support. After data changes target machines and products are automatically selected. For pure installation or for checking of installations targets and products have to be defined. -from REPOSITORY The name of the repository may be defined as default or as a subrepository name of the default repository. -disable This option may be used for removing of postprocessing data, for renaming of devices or for deleting device data. PC's or Linux workstations can be converted with this function from woom to boom or from boom to woom. Some workstation data may be lost by this procedure. Corresponding data fields with different names are woom boom ------------- name2 alias cluster config services subconfig -import FILE SunOS 5.10 Last change: 3 Maintenance Commands WOOM/BOOM(1M) This option enables you to import foreign data sets. The default import file name is ~/oom.list. The import files have a special format. The first character in the file is the field separator. The first line contains the field names as given by the actual option list. The following lines start with the boot/hostnames followed by the data fields e.g. like entsprechend der ersten Zeile folgen, z.B. ;location;config;rgy_hale_login;phone xthf4;2b/220a;zdv;;2753 xthf1;unknown;;;2753 Creating of such a file can be done with a command like boom -list xthf4 xthf1 \ -item location -item config -item phone \ > tst.list If you are working in a team you should use a common directory like ~schroth/equipment/action For supporting multiple entries like xtr++ for defining new terminals in batch, the ready lines will be option- ally removed from the file. If you want to override list items from an import file you must set the preference to import. Otherwise only empty list fields are filled from the import file. If you like to add/remove items to/from array type fields you may prepend the +(add) or -(remove) sign to the argument value. -as DEFREV With this option you can specify a reference device for data operation. The non-spezific data of the reference device has precedence or will be shown addi- tionally. -doom {DB|all|default} With this option you can activate the access to addi- tional data sets. These external data sets are organ- ized under group names like sap or rgy. The name default activates the wboom default, while the name all activates all data sets known to doom. Examples Operative Service Tasks The interactive start of various service task can be done with the following command: gwoom -operating SunOS 5.10 Last change: 4 Maintenance Commands WOOM/BOOM(1M) To restart the spooler on e.g. machine solar03 use the fol- lowing command: gwoom -operating -apply LPSCHED -to solar03 To restart the oracle rdbms and listener processes on enter- prise use the command: gwoom -operating -to enterprise If you are root on a machine you must modify the latter com- mand: /usr/local/bin/gwoom -nolock -operating -to enterprise The latter command is also useful on machines running in our AFS cell but have no standard environment installed. For the special case you are working on a non-X11 terminal you must directly login with rlogin to the machine. Do not use telnet because telnet may pass the DISPLAY variable without your X11-Authorisation. For the special case that the rlogin or rsh/remsh protocol is not permitted, you may try the -secure option to switch to the secure shell protocol. Another special case is applying e.g. REBOOT, SHUTDOWN. NIM.INSTALL or NIM.RESTORE services where you should also use option -nolock in addition to your options, especially if you use woom on the target machine itself. Defining a new xterminal For defining a new xterminal you need to know the right sub- net of the building/room where the terminal will be installed. gboom -list 2b/220a -find xterm If you do not find any devices there you can change to the building/floor algorithm: gboom -list 2b/2 -find xterm Now you can analyse the room and subnet relationships: gboom -list 2b/22 -find xterm -item location -item subnet Now you can interaktively configure the new terminal: gboom -new xtr++ -subnet 214 SunOS 5.10 Last change: 5 Maintenance Commands WOOM/BOOM(1M) Working on service requests If you receive a call or mail on some problems you must identify the machine/device properly with woom (worksta- tions) or boom(xterm, printer, pc, ...). If the customer does not know the name you have a good chance to find the name with the building/room, hardware address, inventory number and/or user name search patterns: gboom -list 55a/ 08001101D331 1017244 User gboom -list 55a/ 08001101D331 1017244 User -ignore printer After identifying you should check the data: gboom -view xtr501 If something is missing or wrong like the location, the phone number or the reponsable person name, you should immediately change the wrong items: gboom -new dummy -phone 3818 -location gebaeude/raum ... You can make further check on the data and the device: gboom -check xtr501 gboom -check xtr501 -verbose

ENVIRONMENT

The following environment variables are supported: WOOMDIRS List of locations BOOMDIRS List of locations LOOMDIRS [loomserver:]loom_lock_directory SITE Used for automatic site customisation. SALAD_ROOT Fallback if no site or env customisation. REMSH Path of the remote shell program.

AUTHOR

This tool is written by Thomas Finnern at DESY/Hamburg. Recommendations and questions may be send to finnern@desy.de

COPYRIGHT

Copyright 1996-1999, DESY/Hamburg This tool may be used freely within the HEP community. There will not be any warranty on the program.

SEE ALSO

loom, gloom, wboom, gwboom, boom, gboom, woom, gwoom, salad, sudo SunOS 5.10 Last change: 6 Maintenance Commands WOOM/BOOM(1M) SunOS 5.10 Last change: 7