Re: copy purge vs. ignore

[Chris (Ducky) Chapin]

Ahhhh! Misunderstood your explanation. Unfortunately, I don't think purge
works the way you wish it to.  Ignore is an option to copy, not purge. The
result being things that disappear from the server, and that which is
prevented from coming from the server (via ignore/exclude) get blown away.

My suggestion would be to use symlinks (seems to be my answer to every
file management puzzle, lately =P ):

Copy the shared files to something like /etc/shared.cron.daily. Then use
links to populate /etc/cron.daily and files to clean it up.

===
control:
   actionsequence = ( copy links files )

copy:
   /cron.daily  dest=/etc/shared.cron.daily
      purge=true
      server=<server_name>

links:   # Make links
   /etc/cron.daily +> /etc/shared.cron.daily type=rel

files:   # Remove broken links
   /etc/cron.daily recurse=1 links=tidy act=fixall
===

The added advantage to this method is you can quickly differentiate the
local from the shared files.

-Ducky

--

 Christopher 'Ducky' Chapin                        ducky@qualcomm.com
 Unix Systems Administrator - Qualcomm, Inc.           (858) 651-5433
 IT Host Services - AE-209F                                 


On Sun, 28 Jul 2002, benf wrote:

> Neither exclude or any form of ignore stops the purge
> from deleting files in the directory that are NOT on the
> server. Basically, it looks like purge overrides these.
> 
> I haven't tried using include to specify the files I want
> distributed, but that would be a hassle as I'd have to remember
> to update the list when changes were made. Hmm, just tried it and
> that doesn't stop the purge from deleting the client-side file either!
> 
> 
> Haven't had time to examine the source yet to see if this is
> a bug or a feature!