Joe had noted that the trailer computers appeared to be sick during the break, which he attributes to problems related to computer crashes in Boulder. When we arrived this morning, we rebooted both "flux" (which had a blank screen that wouldn't react to keystrokes) and "pam" (I don't remember why I rebooted it). "aster" seemed to be fine and once "flux" was up, S+ worked fine. Ling did restart dsm_server on "flux" and then was able to run cockpit using localhost (I think) as the server. We found that printing to "canon" on "flux" and "cannon@pam" on "pam" worked.
"flux" also was just fine when we returned from the field this evening (and I have logged into it from the motel), so we have not yet been able to duplicate the failure. (If we do, I'll first try ssh from my Mac on the same LAN.)
However, S+ wouldn't work on "pam". After some sleuthing, I did "exportfs" and then "/etc/init.d/nfs restart" as root on "flux" followed by "mount /net/local" as root on "pam". (I'm not sure that "exportfs" was necessary.) I'm closer and "pam" can now find "/usr/local/bin/Splus7" (it couldn't before), but I still get an execution permission error. Obviously, I can (and did) ssh from pam to flux to run S+...