| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 477.1 | why not? | SMURF::BAT | Segui la tua beatitudine | Thu Apr 17 1997 21:25 | 17 |
| What messages are you getting from setfiles that indicate that it is
not resetting which file attributes?
It is possible to get too many setfiles errors if you have, for
example, changed your Encodings file, or your MACILBDBASE, or
PACILDBASE, or something similiar. Particularly if you changed the
IR value for syslo.
In EvalLand, if setfiles finds any errors, it should scream at the ISSO
to look more closely at what did not agree with the entries in the
/etc/auth/system/files file. The ISSO can then determine if some user
was being naughty, or it was just some program (read: programmer) not
cleaning up (being naughty).
Normally, you just re-run setfiles and go on your merry way. But
setfiles should fix everything. If it did not, then there is a deeper
question to answer.
|
| 477.2 | I'd like to see what the errors are | SMURF::BAT | Segui la tua beatitudine | Sat Apr 26 1997 00:24 | 2 |
| Bob, when this happens again, and you can afford the time for me to
run down there and look at it, call me.
|
| 477.3 | | ADISSW::FERRARA | | Mon Apr 28 1997 12:39 | 4 |
|
Please stop by anytime (or give a call first)...ZKO2-2/R46
-Bob
|
| 477.4 | Reason: We didn't/don't have the time to do it user-friendly | SMURF::BAT | Segui la tua beatitudine | Mon May 05 1997 23:22 | 27 |
| setfiles was failing with a "cannot set SL..." or "Name SL" on some
directories. The directories were not empty, therefore the directory
label could not be changed (an arbitrary "feature" = poor design
decision [i.e., quick and dirty]) on our part.
To fix it, root (i.e., process SL is syslo and you have allowmac)
has to log in and do:
# mv directory_name directory_name.foo
# cp -p -r directory_name.foo directory_name
(this has the effect of duplicating the directory
contents but now with the syslo SL)
# setlevel -s syshi
(process SL must dominate the directory's SL)
# rm -rf directory_name.foo
# setlevel -s syslo
(set it back so we don't do something else at SL syshi)
# /tcb/bin/setfiles
(until there are no more errors)
Or the functional equivalent.
The problem occurred because setld has not been "MLS+'d". If it had
been, then the fact that the user inadvertantly ran setld and installed
some subset or other while at a process SL other than syslo would not
have had this side effect.
|
| 477.5 | no time for anything | SMURF::BAT | Segui la tua beatitudine | Mon May 05 1997 23:26 | 9 |
| Oh yes, one more thing:
Only the user root is allowed to login if the file /etc/nologin exists.
Evidently setfiles (or the init script, I haven't looked) creates this
file if setfiles fails when run during system startup.
To get rid of it: remove it. (I suppose the init script or setfiles
would delete the file if setfiles runs successfully, but I didn't look
for that either.)
|