Geoff,
"is that not VERY *UX-centric?"
this is a HP forum after all...
Yes, indeed, this _IS_ an HP forum.
But HP _does_ do some more than just HPUX.
And although Tru64 & Linux are pretty much *UX as well, they do _even more_ stuff!
- how do you install software?
Usually, by
-preventing users of that app for one node,
-defining a session trace for a session on that node,
-enabling the needed privs (usually SYSPRV will do, regularly also CMKRNL),
-depending on packaging, either run PRODUCT INSTALL or execute VMSINSTAL,
-enable tis node for applic manager on test data
-if approved, prevent new user sessions on old software version, and allow on new.
SOME products require a special installation account. Oracle has a habit of defining version-specific accounts, some others specifically require "SYSTEM"
- how do you create users?
On smaller sites, by enabling SYSPRV and running AUTHORIZE
At me current assignment, (on avarage 250+ user mutations per day) we have an automated batch running daily, using the personnel system changes as input.
Application granting & revoking (150+ /day) is decentralised to departmental officers who are restricted to just granting to and revoking from established users within their department.
Incidental exceptions (1 or 2 a week) are
done by system management (see above)
- how do you create file systems?
I do not really have that concept. If you mean: specifying various data areas for users or applics and allocating diskspace to that, then, that is integrated into the installation procedures and in the setting up of user environments
I can't think of one reason why I wouldn't want to be root
Well, I guess you have to: in Unix you are either "Mr nobody", or you are "God of the machine". There exist more granular approaches. Just some very simplified examples: "OPER" priv allows/is required for various operator functions, but give no more-than-standard access to the file system or memory.
"SYSPRV" a.o. gives a lot (but not all) access to the file system, but NOT to memory.
"BYPASS" gives FULL control over the file system, "CMEXEC" gives access to the outer layers of the running operating system workings, "CMKRNL" gives full control over it. There are alltogether 35 different, independant privs...
Managers should never have root access - as they don't need to configure the system - if they want root - get them their own box...
I could not agree more! I stlli feel that pain, because I _HAVE BEEN_ in that situation.
And he was the man that evaluated me functioning, upon which was based my paycheck and the continuity of my assignment!
I guess by now it must have become clear that I am a VMS man (or OpenVMS, as Marketing requires it be named).
Wow, must be friday afternoon to make so much fuzz about it.
Really the only point is: This is a HP forum, and that extends to more than just Unix. That should imply that the Unix way is not necessarily the only way. (I even forgot to mention the M$ parts, or printers, or Imaging, but those are all also part of this forum).
Time to travel home, and get some good beer.
While not in person, please join me in thought!
Proost.
Have one on me.
Jan
Don't rust yours pelled jacker to fine doll missed aches.
