We are moving our calendar manager server from a Solaris-2.5 machine to a
Digital Unix 4.0B machine. We moved a few calendars a week ago, and had no
real problems. However, when we moved about 250 users' calendars yesterday,
we had lots of problems.
The rpc.cmsd calendar manager goes out to lunch. It has several failure
modes. Sometimes, and for some users, it simply appears that the calendar
is blank. Other times, we get an rpc program not registered error message
on our clients. The syslog shows that rpc.cmsd exits with a value of either
0xf or (much more often) 0x100. The man page describes exit values
of -1,0,1,2,3. And it says that other return values may be returned by "the
child process". What child process?
Our calendar manager clients are dtcm (the CDE calendar manager) on Digital
Unix and HP-UX, and cm (the OpenWindows calendar manager) under Solaris 2.5
and 2.6. We see the failures on all client types. The server is a DEC 4000
running DU 4.0B.
I am somewhat suspicious that there may be an incompatibility between the
Solaris cm files and the CDE rpc.cmsd.
Has anyone successfully converted from a Solaris calendar manager server to
a DU calendar manager server?
Thanks,
David Ritch
Received on Fri Mar 27 1998 - 06:17:26 NZST