My mistake, thanks Ken. It's just that when you don't do it too often the
names get jumbled together. Beside the fact that '+s' sounds like it should
be sticky.
Jerry Banker
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ken Wallis
Sent: Wednesday,
I used to work at a large IBM site where the customer was running UniVerse on
AIX (no clue what versions). Every night, a cron job would run that would
change the owner to xx1 and the group to xx2 (I don't recall the actual names)
for all the files (and programs) in the UniVerse realm. I
that was my point, easier to remember that +s is that sticky is easier to
remember or associate with +s. Also, unless i don't understand what an OS
is, this program (port.status) is not part of the OS but part of the DB. I
too would not be doing this to an OS program.
On Thu, Sep 4, 2008 at
hey all,
on my linux system when I logto UV I get the uv maint. menu (you
know with categories at the top -- create account ,etc, etc, etc.)
anyway on our aix system when I logto uv I get to TCL and for the life
of me cannot figure out how to get that menu to come up and the admin
Hi,
Check the UV VOC LOGIN record.
There must be a line MOTIF SYSADM.MENU
Usually add a test like this before MOTIF to avoid the menu on these conditions.
IF @TTY = 'phantom' THEN GO END.OF.LOGIN
IF @TTY = 'uvcs' THEN GO END.OF.LOGIN
Also, you can create a VOC MENU entry :
000 MENU
001 PA
To all.
thanks for your suggestions. there was something hincky with aix and
universe. server had been setup in July. Universe added at the same time.
Then in August, we imported our files.And started getting 'universe will
expire in x days'. Which we hadn't been getting before.
Unsubscribe * [EMAIL PROTECTED]
Thank you,
Chris Louis
Asset Management Outsourcing, Inc.
5655 Peachtree Parkway, Suite 213
Norcross, GA 30092
800-893-3501 x 1106
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday,
We are getting the following error when we run a job today, It has been
running for about two weeks and now it failing with the following error.
CRITICAL ERROR! Notify the system administrator.
Abnormal termination of UniVerse.
Fault type is 11. Layer type is BASIC run machine.
Fault
can you vlist the program, and look for address e6? Subject: [U2] Abnormal
Termination of Basic program while calling subroutine Date: Thu, 4 Sep 2008
14:00:23 -0400 From: [EMAIL PROTECTED] To:
u2-users@listserver.u2ug.org We are getting the following error when we run
a job today, It has been
+s = setuid = set user id - is that really hard to remember? What relevance
does the word 'sticky' have to changing the effective user id which a
program executes under?
And someone mentioned fiddling with /usr/bin/ipcs which is part of the OS.
Cheers,
Ken
-Original Message-
From:
10 matches
Mail list logo