search for: purge

..., content => template("nagios/service.erb"), } } then in the server class I have: file { [ "${nagios_dir}/conf.d/", "${nagios_dir}/conf.d/hosts", "${nagios_dir}/conf.d/services" ]: ensure => directory, purge => true, recurse => true, } Exporting the resources works fine, collecting them works great as well. The issue is that once a resource has been exported if it is then removed from wherever it is defined the collected file isn''t purged. I can remove it m...

I am using mdbox storage format. As far as I know, ?doveadm purge? does a complete purge. The time and disk activity would be proportional to the number mdbox files on the storage. The purge time could be huge. I wonder if there is some way of doing a kind of incremental purge, stopping/restarting purging, etc. Purging by file range would be nice too. Advice?...

Is there a way to exec something on purge?

I have a little issue with purging. I use: file { [''/etc/shorewall/puppet'',''/etc/shorewall/puppet/rules'']: ensure => directory, mode => 0700, recurse => true, purge => true, } but purging does not work, i can do a touch /etc/shorewall/puppet/rules/blahblah and the file is not purged at all. I use puppetversion => 0.22.4 i tried also just: file { [''/etc/shorewall/puppet'',''/etc/shorewall/puppet/rul...

I am using stored configs to manage my nagios host and services checks and I have run into a problem that I have been unable to solve. When the stored configs are purged from puppet the nagios server correctly removes them from the services and hosts file but does not notify the nagios service and instead throws an error. So the entries are still there and nagios still reports on them until it is restarted. (/Nagios_service[check_ping_jasontest2.wishabi.net])...

On 24/8/20 7:12, Fabien KOCIK wrote: > First, extract user list using doveadm users '*'. > Then process this list to fit your needs (seven parts for a week and a > part processed by week day for example). > Finally, use -u option of doveadm purge into a loop. This is a good idea for installations with tons of users. Good point. I would be personally interested in incremental purge per user. My personal IMAP account, for instance, has at this moment about 40GB of mdbox files. I keep most of my email for decades, but sure I could free some...

...ot.map.index lmtp(13910): Warning: mdbox /var/mail/virtual/mailbox at domain/mdbox/storage: rebuilding indexes I'm not sure why these mails keep coming back though... or if there's anything that I can do to limit the number of emails that get restored. I want to make sure expunged & purged emails stay expunged & purged. If I run a purge and then force index recreation... why would expunged emails come back? Shouldn't I expect them all to be deleted & purged? Does expunge not expunge all emails? (In production, I'm running autoexpunge but this test below shows what ha...

I have the following define... define puppet::module_dir { if $name { include puppet file { "${puppetdir}/modules/${name}": ensure => directory, mode => 0755, purge => true, recurse => true, } } } I call it like so: puppet::module_dir { "main" } puppet::module_dir { "dev" } ... the creation sense works great. however when I manually create some file in one of these directories and run puppetd I wo...

...service for storing the mails. We sometimes get surges of emails(hundreds or thousands in a couple of seconds). Each alternative request hits a different mail server and then should be replicated. The replication works and we don't encounter missing or duplicated emails. However, when I purge expunged emails, somehow this does not fully remove them when it's setup in this fashion. I ran 2 tests: 1) I send 1000 emails to the loadbalancer(round-robin), expunge on both servers & purge them on both servers, recreate the indexes... ~200 emails come back. 2) I send 1000 emails to...

I have a rather large and active mdbox (28 GB, 3M mess, 1200 deliveries/day). I usually have no problems working with those mails, and there is some batch processing going on (via doveadm). Every few weeks I try my luck running doveadm purge, and this a) crunches about 5GB (to be expected), b) takes rather long (ok), c) leads to long stretches of blocked mdbox, which is the problem. I always turn off the batch processing, but deliveries take so long that they sometimes give up after timeout (they will come back later), and the IMAP cl...

Hi, I think you can achieve file range approach using a small piece of shell script. First, extract user list using doveadm users '*'. Then process this list to fit your needs (seven parts for a week and a part processed by week day for example). Finally, use -u option of doveadm purge into a loop. That is just a trivial first idea. You can notice that it will trigger a doveadm process per user, that seems to be less than optimum approach. According do the documentation (https://wiki.dovecot.org/Tools/Doveadm/Purge), doveadm purge allow using a user *mask* as -u option. This...

...LMTP service for storing the mails. We sometimes get surges of emails(hundreds or thousands in a couple of seconds). Each alternative request hits a different mail server and then should be replicated. The replication works and we don't encounter missing or duplicated emails. However, when I purge expunged emails, somehow this does not fully remove them when it's setup in this fashion. I ran 2 tests: 1) I send 1000 emails to the loadbalancer(round-robin), expunge on both servers & purge them on both servers, recreate the indexes... ~200 emails come back. 2) I send 1000 emails to one...

...that a lot of work has been done regarding doveadm server, but I'm still experiencing easily reproducible segfault crashes of doveadm-server with 2.1.16 when running the following command in a 4 node director/mailbox cluster: /usr/bin/doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -A The dovecot-error.log shows the following errors (addresses anonymized): Apr 29 15:45:14 10.129.3.233 dovecot: doveadm: Error: purge: invalid option -- '' Apr 29 15:45:14 10.129.3.233 dovecot: doveadm(x.xxxxxx at xxx-xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Ap...

Should this work? # --- remove any cronjobs that are not managed by puppet. resources { "cron": purge => true } I get the following error. Resources[cron]: Failed to generate additional resources: You must specify a title for objects of type Puppet::Type::Cron Ben

> > On 24/08/2020 08:30 Jesus Cea <jcea at jcea.es> wrote: > > > > > > I would be personally interested in incremental purge per user. My > > personal IMAP account, for instance, has at this moment about 40GB > > of mdbox files. I keep most of my email for decades, but sure I > > could free some space doing a purge, but I am scared of trying with > > 200.000 mdbox files without knowing how long it...

Running "doveadm purge" with both -D and -v parms, and both -A and -u options, I don't see much in the way of output. doveadm -v purge -u username just returns with no output doveadm -v purge -A returns no output for most users - for my own mailbox it yields "20 / 21" -D returns the same, along wit...

Hi all, Please excuse me if someone has already offered this, but I think the Apt provider should, in addition to -y and -q, also do --purge. This will remove config files and keeps /etc cleaner on the whole. Just a suggestion. Great product and keep up the good work etc. -- Gegroet, Tim (tim|mac or tim|imac on irc)

We've finally (!) started to put some users on mdbox instead of maildir, and now I'm wondering about the purge step. As we're running GPFS for the mailboxes (and dovecot director in front of every dovecot service), is it important to run the "doveadm purge -u $user" on the same host as $user is logged into to avoid index corruption ? If so, will we need to run the "doveadm purge" t...

# 2.1.10: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-44-server x86_64 Ubuntu 10.04.4 LTS doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -A shows the following message in the log when iterating the 49th user: Oct 17 00:47:17 10.129.3.233 dovecot: doveadm: Error: purge: invalid option -- 'e' Oct 17 00:47:17 10.129.3.233 dovecot: doveadm(someuser at example-ll.org): Error: doveadm purge: Client sent unknown parameter: ? Any...

Hi, I do store mail in mdbox format of 150m in size (dovecot 2.3.9). Once in a while I do experience mdbox files of smaller size, even after applying 'doveadm purge' and previous expunges by the users. like: -rw------- 1 vmail dovecot 104854595 Feb 9 2019 /var/mail/.maildirs/userX/storage/m.22 -rw------- 1 vmail dovecot 29088478 Mar 8 2019 /var/mail/.maildirs/userX/storage/m.31 -rw------- 1 vmail dovecot 98210890 Mar 20 2019 /var/mail/.mai...