similar to: centos7 tmpfiles.d deleted outdate files

Hi all, I use centos7 and don't want to use tmpwatch as well as crond. I have a question to use `systemd-tmpfiles-clean.service` with my custom configured file in `tmpfiles.d` to delete outdated files periodically in some log dir. I have a `tmpfiles.d` configured file in `/etc/tmpfiles.d` named `my_log.conf` in following contents. ``` #Type Path Mode UID GID Age Arg r

Would some one help me for this question? thanks very much. On 2016?05?25? 14:18, Qiang Chen wrote: > Hi all, > > I use centos7 and don't want to use tmpwatch as well as crond. > > I have a question to use `systemd-tmpfiles-clean.service` with my > custom configured file in `tmpfiles.d` to delete outdated files > periodically in some log dir. > > I have a

so, there no method to delete special files that below a directory? such as in the directory [root at chenqiang]# tree . ??? test_10d ??? test_20d 0 directories, 2 files [root at chenqiang]# ll total 8 -rw-r--r-- 1 root root 4 5? 20 19:14 test_10d -rw-r--r-- 1 root root 4 5? 10 19:15 test_20d So, I want to delete file test_20d, keep test_10d, how to do that? thx. On 2016?05?27? 02:12,

Hi Jonathan Billings, the `age` can't apply to 'r', only would apply to 'd', 'D', 'x', 'X', etc "The age field only applies to lines starting with |d|, |D|, |v|, |q|, |Q|, |C|, |x| and |X|. If omitted or set to "|-|", no automatic clean-up is done." so, there have good idea if I only want to delete the specific files not all

On Aug 28, 2020, at 17:53, Leon Fauster via CentOS <centos at centos.org> wrote: > > Is cron running in EL8 with stripped CAPs of? Does some one have an > idea to address this? In general, we no longer use tmpwatch at all. In CentOS 7 and 8, use systemd-tmpfiles. Here is a blog post that describes it pretty well:

I have noticed that tmpwatch isn't automatically installed with Centos 7, or at least it wasn't when I set up this computer. I further noticed that the Centos 7 tmpwatch rpm no longer includes /etc/cron.daily/tmpwatch I suspect that at least part of the reason for this is because the /tmp directory is now mounted as a tmpfs by default, so it's automatically cleared when the machine

Hi, I'm moving some old stuff from EL6 to EL8 and one setup has a cron job which uses "tmpwatch -umc $dir" to clean some directories (/etc/cron.daily/tmpwatch). It seems that this triggers this AVC (SElinux mode is enforcing): type=AVC msg=audit(1598576896.772:4267): avc: denied { dac_override } for pid=11013 comm="tmpwatch" capability=1

Commit a6330e9d3af0f5286f1d53d909fd868387b67f69 enabled /run for systemd-tmpfiles: while this works fine in most of the cases, there are few tmpfiles configurations that still references /var/run instead of /run. As result, include also /var/run in the systemd-tmpfiles execution. --- appliance/init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appliance/init

Setup the volatile /run in the appliance also with the tmpfiles configurations available. In particular, setting up correctly the lvm bits allow lvmetad to run. --- appliance/init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appliance/init b/appliance/init index d440007..e678e42 100755 --- a/appliance/init +++ b/appliance/init @@ -88,7 +88,7 @@ machine_id=$(dd

Setup the volatile /run in the appliance also with the tmpfiles configurations available. In particular, setting up correctly the lvm bits allow lvmetad to run. --- appliance/init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appliance/init b/appliance/init index d440007..e678e42 100755 --- a/appliance/init +++ b/appliance/init @@ -88,7 +88,7 @@ machine_id=$(dd

Hi, I'm planning to use dovecot 1.0.5 for a webmail using a lot of user- defined tags. Recently, I just saw the limit of 26 of them when messages are stored in maildir format. This is an important issue for me, since I didn't find how to remove a flag from the dovecot-keywords database. Is there any plan to get rid of the keywords limit ? Or perhaps the new dbox storage format can

Unless I'm mistaken, does it look like Centos 4.7 is missing an update released on December 3rd 2008? Upstream details :- http://rhn.redhat.com/errata/RHBA-2008-0989.html An updated tmpwatch package that fixes various bugs is now available. The tmpwatch utility recursively searches through specified directories and removes files which have not been accessed in a specified period of time.

CentOS Errata and Bugfix Advisory 2015:2002 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-2002.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: de1b31632fe0e1bebe34d864babd654ba929adea7b3da7f0a4f2d7a183de5bd7 tmpwatch-2.9.16-5.el6_7.i686.rpm x86_64:

The main point of this discussion has been that deleting the tempdir() a fixed number of days after its creation is a problem. It should be deleted when the process that created it is done. R attempts to do this, but there are cases in which it does not so a backup is needed. Bill Dunlap TIBCO Software wdunlap tibco.com On Wed, Apr 26, 2017 at 8:46 AM, Brian G. Peterson <brian at

Hi, I use rsync with hardlinks for backup, once a week doing checksums to ensure there's no filesystem corruption in the backed-up data. I also use tmpwatch, or something similar, to clean up /tmp, it removes files that have not been accessed recently. (atime older than some configured limit). I backup /tmp because I throw stuff in tmp that I might possibly need again but don't want to

https://bugzilla.redhat.com/show_bug.cgi?id=1165785 Since the --boot option is relatively new (added 2013-12), I suspect this will break older versions of systemd. However it should be fine for all currently supported versions of Fedora. Rich.

## DESCRIPTION: log_buddy is your friendly little log buddy at your side, helping you dev, debug, and test. ## SYNOPSIS: Call LogBuddy.init to use log_buddy. It will add two methods to object instance and class level: "d" and "logger". You can use your own logger with Logbuddy by passing it into init''s options hash: LogBuddy.init :default_logger =>

Thanks for the answer. The problem that this way is pretty much the same as my find. I want you to be able to delete the file based on the date they were sent to the bin. As I gave in the example: The file has not been changed since 2015, when it is deleted now in 2017, it goes to the bin, dated 2015, when the find pass will erase, why it does not validate when it has been deleted, but the

This is a patch to fix one annoyance of having rsync processes race: I usually keep our servers synced with the following script, run by cron. #!/bin/sh lockfile -r 2 -l 1000 /tmp/synchome.lock || exit 1 rsync -e ssh -avHP --delete zorro01:/home/\* /home >/dev/null rm -f /tmp/synchome.lock -- Sometimes my users (including myself) are in a hurry and syncronise files and directories in their

In article <alpine.DEB.2.20.1705311339370.15080 at ws.sedwards.com>, Steve Edwards <asterisk.org at sedwards.com> wrote: > On Wed, 31 May 2017, Steve Edwards wrote: > > > I want to capture all SIP messages. > > > > I have about 30 hosts in about 6 colos. > > > > My first thought was dumpcap, but the output file name format bugs me. > > >