Kbase 5654: Why super user bit needs set in v5 and v6
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Why super user bit needs set in v5 and v6
920108-jao01
The Super-user bit needs set for _progres and _mprosrv for four reasons
in V5 and has changed slightly in V6. The following are the reasons
and changes:
1. Raw access to the database
In V5 the su bit had to be set for raw access to the database. In
V6 we have switched to osync access (operating system facility
provided by the OS provider) on all platforms that have osync
support. For those platforms which do not have osync support the su
bit is required to be set for raw access.
2. Ulimit
The su bit is required to be set in both V5 and V6 to allow the
session to inherit the su ulimit. Without this, large databases
would not be accessable, since many users have ulimits set smaller
than the system ulimit.
3. Write Permission in db directory
Users often configure their users not to have write access to the
directory which contains the db. Write permission is required to
create the .lk file and setting the su bit allows for this. This
is of marginal value since the write permission goes away after
the session is started.
4. Communication between proshut proserver and mpro
Proshut must have the su bit set so that it can send signals to the
server. The server must have su bit set so that it can send signals
to the clients. If the su bit is not set for these executables,
it will not be possible to shut down the server.
Progress Software Technical Support Note # 5654