T.R | Title | User | Personal Name | Date | Lines |
---|
2199.1 | what about using dcesetup? | FOUNDR::WOODRUFF | | Tue Mar 25 1997 16:02 | 6 |
|
any reason that you're not using dcesetup to configure the client?
it does all the work for you. in fact, you could look at the script
to see the actual commands used to configure the host.
|
2199.2 | | BHAJEE::AIGNER | | Tue Mar 25 1997 18:58 | 16 |
| We have about 60 client machines (and up to 700 in a further extension step).
Each client machine will get the same DCE Client configuration.
I want to perform the configuration job for all clients automatically from a
dedicated machine or within a basic installation (or initial system startup)
procedure for each host, in either case automatically and NOT interactively
(with dcesetup).
This job should be done by a script based on dcecp which I want to write.
Nevertheless, the dcecp command 'host configure' should work correctly.
If there is a better way to do the extensive client configuration
automatically (and/or from a central point), I would appreciate to hear about.
Helmut
|
2199.3 | use dcesetup as a starting point | FOUNDR::WOODRUFF | | Tue Mar 25 1997 19:24 | 21 |
|
> I want to perform the configuration job for all clients automatically from a
>dedicated machine or within a basic installation (or initial system startup)
>procedure for each host, in either case automatically and NOT interactively
>(with dcesetup).
>This job should be done by a script based on dcecp which I want to write.
I would either: write the script to use dcesetup and pass in the cell
info and then run this script on each host
or take the dcesetup script, extract the pieces that are
needed for the configuration, and then run it on each host.
oh, I had heard that with R1.1 - some of the dcecp commands were not
implemented and/or didn't work properly. maybe the configure command is
one of them. (This should be true for all vendors and is fixed with the
R1.2.1 release).
garry
|
2199.4 | Thanks for info | BHAJEE::AIGNER | | Wed Mar 26 1997 09:29 | 17 |
| Is there a list of actually unsupported dcecp commands ?
Can we expect R1.2.1 in the near future ?
I think, for now I'll write my script by extracting the appropriate
commands from dcesetup.
Yet another question to dcesetup:
I've written a script which extracts the DCE version and revision numbers
from dcesetup to show the actual DCE installation (among other things),
as dcesetup does this in it's main menue.
Evaluating dcesetup this way I'm not aware of changes in dcesetup in new
releases. Is there another way to get the DCE version information or may
I get it this way ?
Helmut
|
2199.5 | Version & revision #s | TUXEDO::MAZZAFERRO | | Wed Mar 26 1997 11:32 | 17 |
| Helmut,
In order to retrieve the version and revision #s from dcesetup, you
could execute the following command from the command line:
dcesetup version
which shows both; you'd have to parse the output, of course, to extract
the data of interest.
I don't understand this statement, however :
>> Evaluating dcesetup this way, I'm not aware of changes in dcesetup
>> in new releases.
What types of changes are you interested in or concerned about?
Laura
|
2199.6 | | TUXEDO::MAZZAFERRO | | Wed Mar 26 1997 15:19 | 19 |
| Helmut,
I just checked the DCE V2.0 release notes and there is a statement
in there that says that the following commands are not supported:
host configure
server disable
xattrschema create xxx
cell ping help text is incorrect
cellalias set (disabled)
cdsalias set (disabled)
I'm reasonably sure these are all not supported because they weren't
working in the base code out of OSF.
Most, if not all, should be available in the next release since it
will be based upon a later OSF DCE version that supports them.
Laura
|
2199.7 | Re: DCE client configuration error with dcecp | QUABBI::"rahman@tuxedo.lkg.dec.com" | | Wed Mar 26 1997 19:21 | 66 |
|
In article <2199.4-970326-062914@basesys.dce-products>, aigner@bhajee.enet.dec.com writes:
|>Title: DCE client configuration error with dcecp
|>Is there a list of actually unsupported dcecp commands ?
I don't think we've ever formally put together a list but the
training slides for CSC listed some of the limitations.
|>Can we expect R1.2.1 in the near future ?
We provide dcesetup which does lots more than what the host
consigurations can do out of the box from OSF (setting ACLs,
creating vendor dependent data files, etc). It probably isn't
the best use of our efforts to put everything that needs to be
done in the host config operations in dcecp since dcesetup has
been worked on extensively.
However, what we probably should do is display a message stating
that the user should use dcesetup instead.
|>I think, for now I'll write my script by extracting the appropriate
|>commands from dcesetup.
I am not sure what exactly you are extracting out of dcesetup
and how you are using that information to pass into dcecp but
I can tell you about what we have done to configure hosts
automatically on some of our development machines.
We have created an "input" file containing the proper information
which consists of mostly carriage returns and pass it into
dcesetup as stdin. The "command" file basically contains the
keyboard sequences that one needs to configure client machines.
Thus, create a file with the contents being what you would type
in interactively and then invoke dcesetup under root as following:
% dcesetup < client_config_command_file
Note that the above file will contain the cell password so take
precaution as not to expose it to the world!
|>Yet another question to dcesetup:
|>I've written a script which extracts the DCE version and revision numbers
|>from dcesetup to show the actual DCE installation (among other things),
|>as dcesetup does this in it's main menue.
|>Evaluating dcesetup this way I'm not aware of changes in dcesetup in new
|>releases. Is there another way to get the DCE version information or may
|>I get it this way ?
"dcesetup version" will display the information you need.
"dcesetup show" will display the current configuration on the machine.
You should extract the information you need from the output of
the commands instead of parsing the dcesetup script file as it
will continue to change with every release.
I hope this helps. Thanks.
- Mustie
--
Mustafizur Rahman E-Mail: rahman@tuxedo.lkg.dec.com
Project Leader, DCE for Digital UNIX Phone: (508) 486-5150
Digital Equipment Corporation, Littleton, MA FAX: (508) 486-7417
[posted by Notes-News gateway]
|
2199.8 | | BHAJEE::AIGNER | | Thu Mar 27 1997 14:52 | 12 |
| > .5 - .7
Many thanks for your help.
I've never thought about using dcesetup within a script fed by a configuration
input file (confused by the not-working dcecp command).
With my last examinations I came near this idea.
It will work pretty fine. But I have to hide the cell_admin password as best
as I can.
Thanks again
Helmut
|