Hi Fabio,

Even if the configuration you describe can be implemented with 
robinhood, the philosophy of robinhood cleaning in more based on the 
following inputs:
- What is the average usage level you want to maintain for the 
filesystem (defined by min/max thresholds e.g. 80%/70%)
- What is the min age of files you allow to purge (e.g. last_access > 30 
days).
Based on this, robinhood will ensure an optimal usage of the filesystem 
space, by not unnecessarily cleaning files after 31 days if the 
filesystem can keep 2 months of files
with the specified usage thresholds.
If you run robinhood as a daemon (basically, the same instance as the 
one you use for scanning), it will regularly check filesystem usage max 
threshold and trigger a purge only if necessary,
it will only purge the necessary amount to reach the low watermark, and 
will never purge files younger than the specified duration in the policy.
To make the same instance scan and purge, start it with '--scan' and 
'--purge' options (specify it in /etc/sysconfig/robinhood*)
Or if you prefer, you can also run a "--purge --once" daily in a cron to 
check the usage threshold. Like the daemon, it will only purge if the 
usage is over the high threshold.

Back to what you wanted to do initially:
I think you can merge your three config files in a single one (as the 
merge of config file 1 and 3).
Run the first instance with --scan (or --readlog) option, for example by 
specifying daemon start parameters in /etc/sysconfig/robinhood.
Run the sunday instance with " --purge --once"
Run the daily instance with "--purge-fs=60% --once"

If merging the 3 files doesn't satisfy you, you can avoid duplicate 
configuration
by putting all the common rules and parameters of your three instance in 
a /etc/robinhood.d/<rbh_flavor>/include/common.conf
Then you can include it in specific config files by specyfing "%include 
"include/common.conf" in the specific config files.

Regards,
Thomas


Le 22/01/2015 09:50, Verzelloni Fabio wrote:
> Dear support,
>    I have a question related the best practice how to correctly write a conf 
> file with a particular way of running the purge policy, let me explain, these 
> are our rules for running the cleaning policy:
>
> - every Sunday run the cleaning policy, deleting files older then 30 days
> - every day check if the file system is used more then 60% and in case run 
> the cleaning policy deleting files older then 30 days
>
> Right now I have 3 different configuration files:
> - 1 robinhood instance alway running to simply update the db
> - 1 cron on sunday to run the cleaning policy ( with an ad hoc con file )
> - 1 cron everyday to check if the file system is used more then 60 %  ( with 
> an ad hoc con file )
>
> Is there a way to have everything in one single instance?
>
> Fabio
>
> --
> - Fabio Verzelloni - CSCS - Swiss National Supercomputing Centre
> via Trevano 131 - 6900 Lugano, Switzerland
> Tel: +41 (0)91 610 82 04
>
> _______________________________________________
> robinhood-support mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/robinhood-support
>
>


---
Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce 
que la protection avast! Antivirus est active.
http://www.avast.com


------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
robinhood-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support

Reply via email to