[Info-vax] DNFS1ACP using 100% of CPU

[JF Mezei]

On 13-10-12 20:36, Sum1 wrote:
>
> incorrectly.  I am comfortable that WASD is secure, I am *not* 
> comfortable that Apache is. 

Ok, so this isnt about OS-X but rather about Apache.

The advantage of web servers like WASD and OSU is that it is simpler and
easier to make sure nothing you don't know about is enabled.

Apache, as delivered by Apple, at least back when Apple had servers
(X-serve) came preconfigured to enable tons of sutuff like web mail,
distribution lists etc.

So to "dumb down" Apache to remove any/all unwanted features you would
have to go through all the config files to disable those features.

At the NFS level, VMS can get mighty confused if the remote system
provides NFS information VMS NFS doesn't know how to process.

With VMS NFS behaving, are you able to access the web directories from
DCL without triggering NSG going 100% CPU ? Can you do a dir/full on all
the files the web server is likely to access ?

Does the OS-X directory contain VMS file semantic files ( for instance
temp.txt would be accompanied by some other file (name escapes me now)
which would contain the RMS attributes, and the VMS NSF client would
then provide the VMS app with a temp.txt having  RMS semantics instead
of a raw stream of bytes.

There are settings when you mount a remote disk to decide whether the
VMS  NSF client should handle RMS semantics (forget the actual switches).

 My guess is that you have a couple of files on your OS-X file system
that cause problem when they are fed to the VMS NFS client.