Dear Managers,
I didn't want you to think I had forgotten to summarize, but
in fact no responses have been received nor have I made any real
progress in solving any of these problems other than the workarounds
indicated in my original post. Digital Software Support is checking
the source code for rusers (see #1 in the original post, reproduced
below), but I have not heard back from them yet.
Original post:
Dear Managers,
I recently installed DU 4.0. I've noticed the following
problems and wondered if anyone had suggestions (the hardware is a
3000/600 server and 4 3000/300LX clients):
1) The rusers command is showing many pseudo-terminals in use on the
various machines on my LAN that belong to root and my user account
when I know I am logged out of the machine in question. In some cases
I logged out of the CDE Workspace Manager (sometimes without logging
out of terminal windows since I wanted them to come back up upon
relogin) and in some cases I logged out of a telnet session. Should I
worry about the pseudo-terminals or is this just a problem with
rusers? If I am running out of pseudo-terminals, how do I make them
free again?
2) I am having some trouble with clonefset and rmfset. They work fine
from the command line, but when executed in shell scripts they give
errors like "too many clone filesets" (ONE is too many?). It seems to
be a timing problem; if I put sleep commands before and after the
messages go away. I use these commands primarily to create clone
filesets during backup.
3) When changing a password under C2 security, I received a message
that /usr/bin/spell wasn't available (I enabled "Triviality Checks".).
Surprised that such a old standby was missing, I checked. The (new)
man page is there, but spell (and associated files) is indeed missing
even though it is on the distribution CD. Is this an installation
error or did I miss installing some subset (and if so, the dependence
of C2 security on that subset should be apparent).
4) Yesterday after a long session that involved a lot of graphics, I
started getting messages that "colormap entries couldn't be
allocated". Since many of the entries were probably allocated by long
terminated programs, is there any easy way to clean the colormap up?
Logging out and back in does it, but surely there's an easier way.
Larry
============================================================================
Larry Griffith Dept. of Computer & Info Science
larry_at_garfield.wsc.mass.edu Westfield State College
(413) 572-5294 Westfield, MA 01086 USA
PGP public key available at:
http://garfield.wsc.mass.edu/dcis/griffith.html
============================================================================
Received on Wed Aug 07 1996 - 17:48:41 NZST