Jinfu@cup.portal.com (07/05/88)
I am having this problem for several weeks and still unable to find the cause. What happen is every once a while (about two to three weeks), one of the nodes (DN3000 or 4000) wouldn't be able to create a window pad after login. The DM message window shows a message like 'Cursor is not in proper place' (or something like that) after login with no window pad created. If I use the DM command cp /com/sh, the error message from the DM window would say 'Unable to create new pad'. The only cure I have right now is to reboot the node. This keeps happen to EVERY node at the network for almost the same period of time. Seems like the display manager running out of some kind of resource. I tightened acls a while ago (before the problem occured). It could be some files/directories don't have enough acls, especially the `node_data. However, I already changed acls in that directory and make it wide open (except startup_xxx files). Anyone has any idea about this? Jinfu Chen Motorola, Inc. Internet: Jinfu@cup.portal.com UUCP: ...!sun!portal!cup.portal.com!jinfu