| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 251.1 | correction....... | ACE::BREWER | John Brewer Component Engr. @ABO | Fri Jun 06 1986 16:40 | 3 |
|
...Make paragraph 1 in .0 end as "the backup was overwritten
before the corrupted file was discovered!"
|
| 251.2 | 3 suggestions | DELNI::CANTOR | Dave Cantor | Sat Jun 07 1986 00:43 | 17 |
| Re .0
Three suggestions for getting the numeric UICs from file
ownerships:
1. Rename SYS$SYSTEM:RIGHTSLIST.DAT to a temporary file and
F$FILE to get the UICs; then rename the rights list file
back to the original name.
2. Use F$IDENTIFIER to convert the alphabetic identifier to
numeric UIC form.
3. Use F$FILE(filename,"GRP") and F$FILE(filename,"MEM") for
the numeric group and member numbers. (You'll need to
convert them to octal with F$FAO("!6OL",number) .)
Dave C.
|
| 251.3 | PIP? | BISTRO::HEIN | Hein van den Heuvel, Valbonne. | Sat Jun 07 1986 11:21 | 10 |
| (as in vmsnotes 934.7)
- Does the corruption affect ALL entries after "B"?
Perhaps to file comes back to live somewhere in the
higher key values?
- PIP disk:[0,0]*.DIR/FU could give a list of usernames/Uics.
Hein.
|
| 251.4 | corruption in computers | ACE::BREWER | John Brewer Component Engr. @ABO | Tue Jun 10 1986 13:00 | 11 |
|
re: .3
Yes, all the entries past "B" are corrupted ... to an extent.
The first entry was hosed to the extent that the user couldnt log
in, subsequent entries (in alpha order) can log in, but as a manager
I cat LIST or SHOW them. If I try, I get logged off after exiting
AUTHORIZE.
Strange!
-John
|
| 251.5 | copy the file ... | SWIFT::PITT | Tony Pitt, UK CS, Basingstoke, England | Tue Jun 10 1986 18:09 | 8 |
| Try writing a program to read the UAF sequentially, chucking out
the record you know is bad - you must know which one by now,
presumably! Then write all the other records into another file.
You might be able to recover all but one record that way ... Worth
a try?
T
|
| 251.6 | | PASTIS::MONAHAN | | Wed Jun 11 1986 03:36 | 15 |
| The "logging out" is almost certainly an exec mode bug check
which deletes your process.
The suggestion in .5 is good, but it may be even easier. Try
something like :-
$ CONVERT SYSUAF.DAT /KEY=n SYSUAF.CHECK
$ DEFINE /SYSTEM /EXEC SYSUAF SYS$SYSTEM:SYSUAF.CHECK
If this works (for any "n" up to however many keys SYSUAF has) then
you should end up with a usable authorisation file. You can run
with the logical name set up until you are sure it is reasonably
sane, and then rename SYSUAF.CHECK to SYSUAF.DAT.
Dave
|
| 251.7 | Also, CONVERT /FAST /NOSORT will sometimes fix these | MDVAX3::COAR | A wretched hive of bugs and flamers. | Sat Nov 21 1987 18:24 | 0
|