Technical article 118683

When I try to reset all the permissions of my files using AFPS 4.0.2, the server appears to hang and I have to reboot.

OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written

Problem

I try to reset all the permissions on my files using my Windows 2000, NT4, 98, or 95 edition client, but during this procedure the client locks up and I am unable to log in to my server using telnet or at the console.

To reproduce the problem I double click on "My Computer" and right click my mapped network drive.

Under the Security tab I set all the permissions up how I would like them then click on:

Reset Permissions on Subdirectories Reset Permissions on Existing Files

As the permissions are reset I get the error:

The following error occurred applying security information to ...<file> The session was cancelled.

The server has hung and I am not able to login.  As the permissions
were reset, the server's performance drops as the "lmx.srv" process
uses more CPU time, which can be seen via "ps -efa" and "sar".

Solution

In general, do not select the option to set permissions on all subdirectories and files contained in those subdirectories.

Aside from the fact that it can potentially lead to a large access control list, which in turn leads to poor performance of the server due to the overhead of the ACL lookup task.

In addition, all subdirectories and files automatically inherit their
access rights from their parent directory.  Unless you want all files
and subdirectories to have different access rights, simply setting the
access control on a single top level parent directory is sufficient to
achieve the required access control rights throughout the user's
directory hierarchy.

This problem has been reported to SCO Engineering and a workaround is as follows:

Configure AFPS to not treat the ACL file as a memory mapped file.

The workaround involves the following:

1) Stop the AFPS server with "net stop server"

2) Go to the directory "/var/opt/lanman"

3) Edit the file "lanman.ini" by adding the following line to the "[lmxserver]" section of that file:

mapaclblob=no

This tells AFPS not to map the ACL file in to memory but rather to treat it as a normal disk file.

4) Start the AFPS server with "net start server"

The only possible downside to not having the ACL file mapped in to
memory is reduced performance of the server when checking file
permissions.  In general, this is not noticable unless a very large
number of files are being access in rapid succession (for example,
something searching a heavily populated directory structure for a
specific file, or scanning files for specific contents, or even
setting permissions on a large number of files.  If that kind of
task is not typical of the work being handled by the server, any
performance degradation should not be noticable.

See also

ps(C)
sar(ADM)

From the Xinuos technical article database, record 118683. Reproduced with permission. The original is at www.sco.com/ta/118683, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.