Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!wuarchive!uunet!mcsun!unido!ecrc!ecrc!cmc
From: cmc@ecrc.de (Chris Crampton)
Newsgroups: comp.windows.open-look
Subject: calendar manager database
Message-ID: <1991May23.112737.13619@ecrc.de>
Date: 23 May 91 11:27:37 GMT
Sender: news@ecrc.de
Reply-To: cmc@ecrc.de (Chris Crampton)
Organization: ecrc
Lines: 38

I have a quick question about the calendar manager:
why are the database files for the CM in /var/spool?  Why not
in each user's home directory?  I suppose that this could be
to avoid  a permissions problem as some users protect their
HOME against reading.

Our problem is that we have about 80 diskless clients and so we have about
80 different /var/spool/calendar directories and backing these up does
not fit in very well with our current back-up strategy.  Am I missing the
point or would it be okay to replace all /var/spool/calendar directories
with a symlink to, say, /home/server/calendar which is a globally visible
NFS'ed directory that IS backed up?  i.e. for all clients:


	# mv /var/spool/calendar/* /home/server/calendar
	# rmdir /var/spool/calendar
	# ln -s /home/server/calendar /var/spool/calendar

Or would it be okay to add something like the following to each client's
fstab:

server:/home/server/calendar  /var/spool/calendar  nfs bg,rw,intr 0 0


Thanks for any help,

Chris.



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

Chris Crampton.			uucp:  cmc@ecrc.uucp
				       ..!unido!ecrc!cmc
ECRC GmbH		    Internet:  cmc@ecrc.de
Arabellastrasse 17
D-8000 Munich 81
Germany				Tel.:  +49 89 92699  138