Very Computer

thanks in advance,

cat << EOF > /var/spool/calendar/callog.bwang
Version: 1
**** start of log on Sat Aug 28 04:01:13 1993 ****

EOF

Some people have the impression that the original UNIX work was a bootleg
project, a "skunk works." This is not so.  Research workers are supposed to
discover or invent new things.... Our intent was to create a pleasant
computing environment for ourselves, and our hope was that others liked it.
        - Dennis M. Ritchie, 1983 Turing Award Lecture

I'm having the same problem.  I rm it daily, but I'd like to make it go away
permenently.  Anyone know what creates it??  Thanks in advance.  
btw, I'm on Solaris 2.2..

--

Fluent Inc.  10 Cavendish Court  Lebanon, NH  03766-1442  (603)643-2600        

My original problem:

I am running SunOS 4.1.3 and NIS. I encountered this error in OW3 when
the machine's name configuration was wrong. The "hostname" command
returned a fully-qualified domainname, but the machine thought it was
still just the specific name of the host (tpm-sprl in my case). Once it
was fixed to resolve correctly, and cm was run again, there was no
problem. I don't know if this is your problem, but it looks similar
--------------------------------------------------------------------------

The problem is that 2.2 calendar manager does not create
/var/spool/calendar/callog.<user>. Put the following in under your
user name, set the permissions to 640 owner=<user> group=<daemon>.
I'm not sure if you need the (access exec ...) rule. Restart rpc.cmsd,
and you're up.

cat << EOF > /var/spool/calendar/callog.bwang
Version: 1
**** start of log on Sat Aug 28 04:01:13 1993 ****

EOF

--------------------------------------------------------------------------

Beichang Wang,
        Just from the symptom I would guess a permissions problem.  cm is
Dear Beichang Wang,
        Just from the symptom I would guess a permissions problem.  cm is
trying to create a file and cannot.  Check the permissions to make sure cm
can open a file where it is trying to.  Does the calendar file belong in the
user's directory, or somewhere in /usr/spool, or what (I don't run cm myself).

I hope this suggestion helps.

--------------------------------------------------------------------------

 The calendar manager works after creating /var/spool/calendar/callog.bwang
 file. But only on the machine that has /var/spool/calendar/callog.bwang file.
 There are several dataless machines in my network. Every dataless machine has
 its own /var/spool. This means I need to create callog.bwang file on every
 machine. Is it right? If not, what is the way? I checked permissions of all
 related directriy and files. They are same as what the answerbook said. I
 followed the instrctions in the "Solaris 2.2 Users Guide" to set calendar
 access list, permissions, and switched the nickname and name of the
 hostcomputer, but still can let calendar manager work properly. Is there a
 way to maintain all users calendar information on a server and user can login
 to any machine to run calendar manager correctly?

thanks to all those who answered,

Beichang Wang

 my server

I think removing them both may rid you of them permanently.

Casper

Almost certainly, sometime since you installed the OS, you have given
your machine a new inet number. This number now no longer agrees with
the corresponding numbers in /etc/saf/tcp/_pmtab.

You should find lines similiar to these in the _pmtab file...

lp::root:reserved:reserved:reserved:::p::/var/spool/lp/fifos/listenS5#
lpd::root:reserved:reserved:reserved:\x00020203c0be4b270000000000000000::p::/var/spool/lp/fifos/listenBSD#
0::root:reserved:reserved:reserved:\x00020ACEc0be4b270000000000000000::c::/usr/lib/saf/nlps_server#

The two long lines of hex numbers include your inet number encoded in
hex. In my case the 'c0be4b27' is my inet number of 192.190.75.39
        192 == c0
        190 == be
        75  == 4b
        39  == 27

do a similiar conversion on your inet numbers, then *carefully*
replace the corresponding digits in these two lines. Make certain that
you don't delete too much, or add in too much, ("wc -c" should report
the same before and after).

Note: the conversion is simple if you use the command "dc" then set
dc's output to hex....

dc
16 o
192 p
190 p
75 p
39 p
^D

is what I did.

Once you have fixed this file, you will have to reboot. I don't
remember if you have to delete the ?tmpx files or not.

-Larry