The question is probably what network ports Pro/PDM??? uses. AFS uses
ports in the 7000-7010 range, most likely 7000, 7001, and 7003 in the
cache manager itself. If their product is trying to use those ports as
well for their RPCs, then things could well be screwed up. There has to
be a way to keep their RPCs from using those port numbers, but that will
depend on what they're doing to select port numbers for their RPC
programs. And it might, or might not, be tough to change the PTC
products not to use colliding port numbers.
As far as other problems, there are the standard issues of AFS not
observing the mode bits for Unix protections, AFS groups not being the
same as Unix groups, byte-range locking not being supported,
non-``standard'' (non-automounter) semantics for mount points,
non-cheapness of stat()'ing every file in the /afs/ directory, slightly
different st_dev/st_rdev/st_fsid results, AFS files not being stored
back on a server until close() or fsync(), the fact that close() can
return error codes, and that codes such as ETIMEDOUT might be returned
from syscalls whose callers don't expect it. Other than that, and
whatever else I've forgotten, there shouldn't be much of a problem.
Craig
