This might not be the right place to ask this question, but I'll give it a
shot.
I'm attempting to use the CDE calendar program (dtcm). The problem I'm
having is when I attempt to create a To-Do item. When I click on "Insert"
in the To Do Editor dialog I get the error: "Unknown error. Operation was
cancelled." If I click on the "Help" button in the error message dialog
I'm brought to calendar help with the message "Nonexistent location ID:
CalendarBackEndError." I get exactly the same effects if I attempt to
create an appointment.
In the past everything worked fine. However at that time I was not
interested in using the system so outside a little playing around I didn't
do much with it. Now I'm looking at the system again a bit more seriously
and it's not working.
There has been one significant change since the days when it worked: I
have moved the /usr/var file structure to a file system of its own. In
particular I did this (in single user mode):
1. Created a partition on a new disk to hold /var.
2. Using tar I copied all files from /usr/var to this new partition.
3. I renamed /usr/var to /usr/var.old
4. I mounted the new partition as /var (deleting the symbolic link to
/usr/var that used to be there) and I created a symbolic link /usr/var
that points to /var
This basically seems to work *except* I noticed that tar did not copy the
sticky bit that was set on some directories. Using find I located all
directories in /usr/var.old with the sticky bit set and I manually set
permissions and ownerships on those directories in the new /var file
system. There were only a few such directories, but one of them was
obviously related to the calendar system. I expected that would fix the
problem, but it has not.
I also verified SUID and SGID files/directories. It's handy that I still
have a copy of the original /usr/var as /usr/var.old!
Anyway, my guess is that my problem has something to do with the
organization of this new filesystem, but I'm not sure what. Sice I'd like
to blow away /usr/var.old soon (to recover disk space) I want to get this
matter resolved. I don't want to delete /usr/var.old until I am sure I'll
no longer need it!
P.S I'm using DU v4.0B with jumbo patch 5 applied. It is also true that
the system has been upgraded from 4.0A since the days the calendar worked.
Could the problem really be related to the upgrade and/or patch kit?
During the upgrade I did remove a few packages that I believed I didn't
need. Is there anything I should check with setld?
TIA
*****************************************************************************
Peter
pchapin_at_twilight.vtc.vsc.edu
http://twilight.vtc.vsc.edu/~pchapin/
"Don't fix the program. Fix the specification."
Received on Mon May 11 1998 - 17:41:18 NZST