similar to: cron mystery

For some reason I cannot fathom, cron.hourly runs twice each hour on one of my two CentOS-5.4 systems, as reported in /var/log/cron: ------------------------- Mar 16 14:01:01 helen crond[27833]: (root) CMD (run-parts /etc/cron.hourly) Mar 16 14:01:01 helen crond[27834]: (root) CMD (run-parts /etc/cron.hourly) ------------------------- On the other it just runs once, as expected.

I'm trying to setup sendmail/dovecot on a new server running CentOS-6 (well, CentOS-6.2 now). Everything seems to go well, but when I run fetchmail I get this warning: ------------------------------------ [tim at grover ~]$ fetchmail imap.maths.tcd.ie fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!) ------------------------------------ I should

Is one meant to have one or the other? If so, which is recommended? I have -------------------------------- [tim at helen etc]$ cat anacrontab # /etc/anacrontab: configuration file for anacron # See anacron(8) and anacrontab(5) for details. SHELL=/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root 1 65 cron.daily run-parts /etc/cron.daily 7 70 cron.weekly

I have a strange problem on a CentOS-5.8 machine. I can only login as root. If I try to login with one of the user's names, it hangs for a long time. I thought it hung forever, but I just found that I do login after "su tim" after 5 minutes. It seems that the problem lies in repeated messages in /var/log/messages --------------------------- May 3 12:14:13 helen su: nss_ldap: failed

hello list!! I'm attempting to find out why this cron job isn't running. the host is centos 5.6 on i386 just so you know. 0 3 * * * /bin/alldb > /home/bluethundr/backupdb/alldb-$(date +%Y%m%d%H%S).sql The job is meant to backup all the databases on a mysql server every day at 3 am. I have checked the backup directory and nothing is showing up for those

I don't understand Windows permissions under Samba. I am running an smb server under CentOS-5.4, and have a Windows XP Pro machine ("harriet") as a client. I have set up shares C and D on harriet corresponding to the 2 drives C: and D: on the machine, and I have asked that files should be shared. Now when I mount harriet:C I can see the top level folders, but cannot see Documents

I don't understand Windows permissions under Samba. I am running an smb server under CentOS-5.4, and have a Windows XP Pro machine ("harriet") as a client. I have set up shares C and D on harriet corresponding to the 2 drives C: and D: on the machine, and I have asked that files should be shared. Now when I mount harriet:C I can see the top level folders, but cannot see Documents

I'm getting repeated email (KMail) error messages about one apparently over-large post: -------------------------- Received: from helen.gayleard.com (localhost.localdomain [127.0.0.1]) by helen.gayleard.com (Postfix) with ESMTP id E4500294A0 for <tim at helen.gayleard.com>; Sat, 24 Jan 2015 14:00:05 +0000 (GMT) Received: (from tim at localhost) by helen.gayleard.com

I've been getting a few avahi-daemon errors in /var/log/messages, eg ------------------------------- Jan 11 00:40:24 helen avahi-daemon[12732]: Invalid query packet. Jan 11 00:40:29 helen last message repeated 17 times ------------------------------- (This is

hey centos long time no hear! :) I'm having a small issue where the backup jobs that I set to run in the crontab of the backup user do not appear to be running. Here's how I set it up (with crontab -e as the backup user): run amanda every night (check at 2:45 and backup at 3) 45 2 * * * /usr/sbin/amcheck /var/log/amanda/crontab/amcheck.log * 3 * * * /usr/sbin/amdump

On Tue, Oct 13, 2015 at 2:35 PM, Jonathan Billings <billings at negate.org> wrote: > On Tue, Oct 13, 2015 at 02:04:49PM +0000, C. L. Martinez wrote: >> And according to systemd, without problems: >> >> crond.service - Command Scheduler >> Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled) >> Active: active (running) since Tue 2015-10-13

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

The mirrorlist entry in my Fedora-11 /etc/yum.repos.d/fedora-update.repo reads: mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=updates-released- f$releasever&arch=$basearch As far as I can see, this means that yum is looking for the file metalink at mirrors.fedoraproject.org ? If I try "sudo yum update" I get: ----------------------------------- [tim at elizabeth ~]$

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.

> On Mon, 6 Apr 2020 at 06:59, Tobias Kirchhofer <collect at shift.agency> > wrote: > >> 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: >> >> >>

> Date: Thursday, July 20, 2017 02:25:52 +0000 > From: Richard <lists-centos at listmail.innovate.net> > >> Date: Wednesday, July 19, 2017 23:31:10 +0000 >> From: Chad Cordero <ccordero at csusb.edu> >> >> It?s being rejected before it even reaches the mailbox, so >> forwarding won?t work.? Crond should really be using the MAILTO >>

It?s being rejected before it even reaches the mailbox, so forwarding won?t work.? Crond should really be using the MAILTO variable and it?s not. --- Chad Cordero Information Technology Consultant Enterprise & Cloud Services Information Technology Services California State University, San Bernardino 5500 University Pkwy San Bernardino, CA 92407-2393 Main Line: 909/537-7677 Direct

Hi all, Who takes care of cronjob in /etc/cron.d ? Should we tell crond to run it? /etc/crontab only mentions hourly, daily, weekly, monthly -- Thanks Fajar

Hi all, I've had this error rear it's ugly head again and I'm not exactly sure why. The output in /var/log/message is: crond[14764]: pam_loginuid(crond:session): set_loginuid failed opening loginuid crond[14765]: pam_loginuid(crond:session): set_loginuid failed opening loginuid crond[14811]: pam_loginuid(crond:session): set_loginuid failed opening loginuid

I've been collecting redhat.fedora from gmane for several years, but about a week ago I found that while I could read gmane newsgroups I was unable to post to them - that is, my posts did not appear. I was able to post to gmane.test, and could read these posts. So I assume there is no problem with my From: or other headers. I take it that the gmane.linux.centos.general is in fact