QUESTION:
DSMIT requires to change password sequentially. I have several questions
1) what does dsmit -f flag do? In the DSMIT guide and reference manual,
it says, it redirects std-in and std-out for smit commands. How can
I use this flag..show me an example.
2) how can be redirect the input to smit commands from a file instead
of a keyboard...so that dsmit will not prompt user to type password
for each client..but will read it directly from this file.?
Having to enter the required data from the keyboard is unacceptable
where you have working collectives as large as 300+ clients.
Any way to automate changing passwords, etc..
4) If I select to install products from the tape, Does DSMIT require
tape be in the client's machines tape drive or does it use the tape
from the server.?
---------- ---------- ---------- --------- ---------- ----------
A: The -f flag of DSMIT (and likewise, for SMIT) redirects ALL standard
input and all standard output as specified -- not just for individual
commands.
For instance, if you were on the hft, you could do something like:
dsmit -f < /dev/tty0 > /dev/tty1
This would display all output on tty1, while accepting standard input
from tty0. In this example, suppose you would try to change a
password. DSMIT (and SMIT) both use the "passwd" command to do this.
The passwd command does not read standard input, but only input coming
from the session in which DSMIT was activated. Thus, you would still
have to type the password in on the hft even though standard input has
been redirected from /dev/tty0. Thus, you would be unable to read the
passwords from a file, since "passwd" does not use stdin.
An alternative would be to use ASKQ item CCMBG. This will allow you
to automatically add passwords to one system. You could then execute
this script to each client individually (without using DSMIT). While
this will be longer than what you had in mind, it will be much faster
than typing in each password individually on each system one at a
time.
DSMIT executes all commands as if they had been executed on each
client individually. Thus, if you want to install a product, DSMIT
will send the normal installp command to each client, and would
therefore require that each client have its own tape drive. An
alternative is to make the DSMIT server into an installation server.
Then you could install the images to disk, have all the clients mount
the install images, and then install them simultaneously.
---------- ---------- ---------- --------- ---------- ----------
This item was created from library item Q658682 CRHLK
Additional search words:
CLIENTS CRHLK DSMIT INPUT IRECTING IX MANAGEMENT MAY94 MULTIPLE OP
OUTPUT OZNEW QUESTION RED RELATED RISCMGMT RISCSYSTEM SOFTWARE SYS
SYSTEM
WWQA: ITEM: RTA000042111 ITEM: RTA000042111
Dated: 03/1996 Category: RISCMGMT
This HTML file was generated 99/06/24~12:43:16
Comments or suggestions?
Contact us