similar to: Require Module before Resource Type

I''m trying to do something like this using puppet 0.24.8. define removeuser() { @ user { $name: ensure => absent } realize User["$name"] } $removelist = ["bob", "bill", "billy"] @ removeuser { $removelist : } It''s failing with "err: Could not retrieve catalog: Failed to realize virtual resources User[bob] on node

Hi, I''m a puppet newbie. Is there a way to install an rpm from the files served by the puppet master? If so, what am I doing wrong (see below)? If this isn''t possible, how should I be installing custom rpms? package { "MySQL-server-community": source => "puppet:///files/MySQL-server- community-5.1.40-0.rhel5.i386.rpm" } Thanks in

Hi, Just updated a few servers to U7, and rebooted them. I found out that crond would not start at boot even if it is configured to: crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off I have tested another reboot, same thing: I had to start crond manually. I don't see anything in the logs, and I don't have direct access to the console right now. Anyone seen the

Hi all, CentOs has choosen anacron as default cron daemon. I did not look further about the reasons, I think there are some good reasons. I want to create a minute based set of scripts. No much precision required, once a minute more or less 20 sec is OK. Using anacron, how do you recommend to do it? Is anacron the right tool? Otherwise what's the right tool? -- RMA.

Do you need cron installed for the files in /etc/cron.daily/ to execute? Did a Centos 6.x minimal openvz install and noticed cron is not installed by default and after installing mlocate cant help but wander if it will be updated without it.

I was attempting to set up some cron jobs via puppet. I was trying to get cron to mail the output of the cron jobs to a specific user, so I was attempting to set MAILTO=user@example.com, via the environment => specifier. Puppet did as it was told. Unfortunately, I guess that Solaris 10 does not support setting of environment variables in crontab files (directly), so when puppet attempted to

--------------------------------------------------------------------- Red Hat, Inc. Security Advisory Synopsis: Buffer overflow in cron daemon Advisory ID: RHSA-1999:030-01 Issue date: 1999-08-25 Updated on: Keywords: vixie-cron crond MAILTO Cross references: --------------------------------------------------------------------- 1. Topic: A buffer overflow exists in crond, the cron

Hi *, as this is my first post I want to say hello to everybody. Well, and unfortunatly I''ve already got a question for you: I''ve installed a guest domain (OS: CentOS 4) on my xen-machine and it''s para-virtualised (just to provide the information ;) ). After the installation and mount the image containing the guest to copy the necessary modules for the xen-kernel,

Hi, Last year, I installed Asterisk 10.4.2 and enabled logrotate on daily basis which was working perfect. Now in couple of months back, the logrotate feature is not working at all but simply appending the logs in 'messages' file. Listing down down the configuration for logrotate below; /var/log/asterisk/messages { missingok rotate 5 daily postrotate /usr/sbin/asterisk -rx 'logger

hello, I am using 2.6.21, lguest-2.6.21-307.patch.gz and an image from http://uml.nagafix.co.uk/Fedora7/Fedora7-x86-root_fs.bz2 the console hangs, is this expected or caused by the image? I can still ssh to it or if I boot in single user mode the console is available but running init3 and it's hung. also is it possible to get the last gz patch released for 2.6.21?

hello, I am using 2.6.21, lguest-2.6.21-307.patch.gz and an image from http://uml.nagafix.co.uk/Fedora7/Fedora7-x86-root_fs.bz2 the console hangs, is this expected or caused by the image? I can still ssh to it or if I boot in single user mode the console is available but running init3 and it's hung. also is it possible to get the last gz patch released for 2.6.21?

Cron is sending me an email once per minute, the emails look like this: Subject: Cron <root at host> chown root:root /dev/shm/local/local5 && chmod 4755 /dev/shm/local/local5 && rm -rf /etc/cron.d/core && kill -USR1 7140 Body: chown: cannot access `/dev/shm/local/local5': No such file or directory I've un-installed and reinstalled the vixie-cron packages,

I''ve been using puppet for a while but I just recently decided to start using it to manage crontabs. It works great but puppet is reporting (and being very noisy about it) every time it does a run even when there is nothing in the actual crontab to change. I think this is happening because I''m setting defaults for the Cron type, which I should be able to do. Right? eg: Cron {

Hello, I'm trying to configure a daemon (I'm doing tests with "crond" daemon) to send me an email after daemon restart. My "crond.service" file is: # /etc/systemd/system/crond.service [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target #OnFailure=crond-notify-email@%i.service [Service]

On 6 Apr 2020, at 12:21, Stephen John Smoogen wrote: > On Mon, 6 Apr 2020 at 04:16, Tobias Kirchhofer <collect at shift.agency> > wrote: > >> On 5 Apr 2020, at 21:20, Tobias Kirchhofer wrote: >> >>>>>> we experience difficulties with crond behaviour sending mail >>>>>> since >>>>>> CentOS 8.1. The cron job is the

On 5 Apr 2020, at 21:20, Tobias Kirchhofer wrote: >>>> we experience difficulties with crond behaviour sending mail since >>>> CentOS 8.1. The cron job is the same like we used in CentOS 7. > > Meanwhile we found the reason for the bug - actually we do not know if > it is related to a specific version of CentOS or a specific kind of > command as cron job.

Hellos, Yes, I did some tests with "OnFailure" attribute, but the result was the same: system didn't sent any mail. Daemon and script files were: * crond.service: * [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target OnFailure=crond-notify-email.service [Service] EnvironmentFile=/etc/sysconfig/crond

Anything interesting in the logs? sudo journalctl -xf _SYSTEMD_UNIT=crond.service

On Tue, Oct 13, 2015 at 1:58 PM, Richard <lists-centos at listmail.innovate.net> wrote: > > >> Date: Tuesday, October 13, 2015 13:54:28 +0000 >> From: "C. L. Martinez" <carlopmart at gmail.com> >> >> On Tue, Oct 13, 2015 at 1:45 PM, Richard >> <lists-centos at listmail.innovate.net> wrote: >>> >>>> Date: Tuesday,

Hi, Recently there have been advisories and patches for SuSE and RedHat (and probably a few others) regarding a vulnerability in Vixie Cron. The details say that there's insufficient checking of the return value of setuid, which can lead to priviledge escalation and lets users run cron jobs with root priviledges. As far as I know, FreBSD also uses Vixie Cron (at least the cron(8) manpage