HP3000-L Archives

March 1998, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Vance <[log in to unmask]>
Reply To:
Jeff Vance <[log in to unmask]>
Date:
Tue, 17 Mar 1998 16:21:29 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (43 lines)
On Mar 17, 11:22am, Rick Tomlinson wrote:
...
> Now that we have a user vol set, the goal is to keep the user
> data on the user vol set.  However, programmer's often forget and just
> enter NEWGROUP <groupname> without specifying the ONVS option.  Also,
> update/install jobs often run add groups and do so without regard to
> user vol sets.  Of course, this uses up space on the system vol set.
> Has anyone else run into this problem?

I know of several large customers who have the same basic problem: their
developers need to be able to create groups, but they forget to specify the
VS name or they intentionlly bypass VS limits by creating the groups on
the system volumeset.

My goal in creating the NEWACCT and NEWGROUP UDCs (on jazz) was primarliy to
address your concern.  Using these UDCs the SM only needs to specify the
:newacct command once and automatically: 1) the account is created on the
system volset with FILES=0, 2) the account is created on the target volset
3) the PUB group on the system volset has FILES=0 applied and is homed
to the target volset, and 4) the PUB group is created on the target user
volset.  But you only needed to entry a single NEWACCT command.

SMs and AMs also need only enter the :newgroup command once. 1) the group
is created on the system volset, 2) the group is created on the appropriate
user volset, 3) the group on the system volset is homed to the user volset
4) if the parent account has not been created on the user volset, and the
user has SM cap, the account will also be created on the target volset.

The appropriate user volset is determined by a config file that maps
group or acct names to a volumeset.  This config file can be automatically
created via a supporting script, or you can use an editor.  If the config
file is missing or if there is no match for the desired group (or acct),
the user is prompted for the correct volset name.  At this point the user
can also append this new volset mapping to the config file so it is easy
to keep it current.

I am willing to enhance the UDCs to meet your needs.

Regards,
Jeff Vance, CSY

--

ATOM RSS1 RSS2