Re: Unsupported three-architecture cluster
- From: JF Mezei <jfmezei.spamnot@xxxxxxxxxxxxx>
- Date: Mon, 31 Dec 2007 13:40:18 -0500
Rich Jordan wrote:
Given the huge difference in account quota recommendations between the
three architectures, and the significant number of shared accounts
(user, system, tcpip, webserver, etc, most of which are shared between
How much software runs on the vax ?
In my case, I just upped the SYSUAF to match the alpha requirements. In
the end, the big changes are with the pgflquota which alpha needs <carl
sagan> billions and billions</carl sagan> of. On the VAX, you can use
the sysgen WSMAX to limit working sets to a reasonable limit.
If you don't have much software running on it, it may be sufficient, and
just lest the process/memory manager decide how much working set each
process really deserves.
Another option would be to have an architecture specific SYSUAF during
startup that includes only the necessary accounts with that
architecture's quota, and once startup is complete, you then redirect
SYSUAF to the shared one where all the usernames are defined. SOftware
that is started at boot time would get "OK" quotas, but processes
started after boot would get the exagerated quotas that would be allow
one to run on any platform.
Another approach is to look at the actual startup scripts for each
layered product. Many would provide ways to specify quotas
because in the end, they dur a RUN/DETACHED and provide the quotas in
that command line.
.
- Follow-Ups:
- Re: Unsupported three-architecture cluster
- From: Rich Jordan
- Re: Unsupported three-architecture cluster
- References:
- Unsupported three-architecture cluster
- From: Rich Jordan
- Unsupported three-architecture cluster
- Prev by Date: Unsupported three-architecture cluster
- Next by Date: RE: Samba Gains Legal Access to Microsoft Network File Protocols
- Previous by thread: Unsupported three-architecture cluster
- Next by thread: Re: Unsupported three-architecture cluster
- Index(es):
Relevant Pages
|
