HP3000-L Archives

February 1997, Week 2

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:
Terry Prime <[log in to unmask]>
Reply To:
Terry Prime <[log in to unmask]>
Date:
Wed, 12 Feb 1997 12:56:01 +1100
Content-Type:
text/plain
Parts/Attachments:
text/plain (42 lines)
>Date: Wed, 12 Feb 1997 11:51:05 +1100
>To: Jeff Kell <[log in to unmask]>
>From: Terry Prime <[log in to unmask]>
>Subject: Re: [HP3000-L] still a udc problem
>Cc: raven
>
>I have granted read any for the udc and the group, secured the udc, and
still, as you try to log on it says that you can not access the system udc.
>SECURITY VIOLATION FSERR93
>COULDN'T OPEN UDC FILE UDCFILE.GEN.SYS (CIERR 1923)
>NO SYSTEM LEVEL UDC'S HAVE BEEN INITIALIZED (CIWARN 1929)
>
>regards  ...  Terry
>At 08:16 PM 2/11/97 -0500, you wrote:
>>Prior to 5.5, a UDC file *must* have read/lock permissions.
>>On 5.5, a UDC file can get away with execute permissions (not sure about
>>lock, I've already asked Jeff Vance offline.  I think UDC files just
>>need read or execute on 5.5; but command.pub.sys needs read/lock).
>>
>>In other words, I'm not certain Lock access is an issue.
>>
>>You need read access to any UDC file prior to 5.5.
>>
>>You need read or execute access to a UDC file on 5.5
>>
>>Same rules apply to command files too.
>>
>>Jeff Kell <[log in to unmask]>
>>
>>
>
Signature:
     Terry Prime
     Client Services Officer
     Queensland University of Technology
     phone: (07)38641784   fax (07)38641343
     Internet:[log in to unmask]

Disclaimer:
     What i have said is my opinion and does not reflect the
     opinion of my employer or co-workers

ATOM RSS1 RSS2