similar to: Cron Issues

Check selinux context for directory? 30.4.2015 12.19 ap. "Matt" <matt.mailinglists at gmail.com> kirjoitti: > I have noanacron installed on a fresh centos 7 install. > > I added this too settings. > > nano /etc/cron.d/0hourly > > */5 * * * * root run-parts /etc/cron.fiveminutes > */1 * * * * root run-parts /etc/cron.minute > 0,30 * * * * root run-parts

When I have multiple scripts in /etc/cron.hourly/ using noanacron do they all start at same time or sequentially? I would rather they all went at same time in case one takes close to an hour to complete.

> 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 >>

>> But instead i get >> centos: sshd[7929]: pam_unix(sshd:session): session opened for user >> <username> > > "pam_unix" should be an indication that <username> appears in the local > unix password files. Make sure that it doesn't. Nope. None of the usernames i tried is in /etc/passwd or /etc/shadow > > What do /etc/pam.d/sshd and

On 05/09/2015 01:24 PM, Jonathan Billings wrote: > Is it normal to have pam_unix and pam_sss twice for each each section? No. See my previous message. I think it's the result of copying portions of SuSE configurations.

On 04/26/2017 04:22 AM, Gordon Messmer wrote: > On 04/25/2017 03:25 PM, Robert Moskowitz wrote: >> This made the same content as before that caused problems: > > I still don't understand, exactly. Are you seeing *new* problems > after installing a policy? What are the problems? > >> #!!!! The file '/var/lib/mysql/mysql.sock' is mislabeled on your system.

one more thing: firewalld service and selinux are deactivated. On 05/11/2015 07:06 PM, Ulrich Hiller wrote: > Hmmm...., i have made now a complete new install but the problem > persists: ldap authentication works, but the host attribute is ignored. > > I have installed CentOS7 64bit with KDE. > I did not do any 'yum update' or install of extra packages so far. > >

On 10/14/2015 06:42 PM, Gordon Messmer wrote: > On 10/14/2015 07:09 AM, C.L. Martinez wrote: >> Uhmm ... that is not what I expect: >> >> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system >> /run/user/1000/gvfs >> Output information may be incomplete. >> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME >> systemd

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

There seems to be a problem in the way `+` is dispatched for POSIXt/difftime (R 2.8.0 Windows). With the following definitions: t0 <- as.POSIXct('2009-01-01 00:00') halfhour.mins <- as.difftime(30,units='mins') I would have thought that the straightforward answer to Suresh's question would be something like t0 + halfhour.mins * (0:47) And indeed, if we

Hello, There's a file server running CentOS 7 with packaged Samba: # rpm -qi samba Name : samba Epoch : 0 Version : 4.10.4 Release : 11.el7_8 Architecture: x86_64 ... Source RPM : samba-4.10.4-11.el7_8.src.rpm Build Date : Tue 12 May 2020 04:31:13 PM UTC ... Packager : CentOS BuildSystem <http://bugs.centos.org> When a user opens a file share, there's an

Well, I feel silly.? There are three places MAILTO can affect crond: /etc/crontab, /etc/crond.d/0hourly, and /etc/anacrontab.? Once I set this in these 3 files, I started getting mail from crond.? Thank you all for your help. --- Chad Cordero Information Technology Consultant Enterprise & Cloud Services Information Technology Services California State University, San Bernardino 5500

>>>>> "Marc" == Marc Schwartz <mschwartz@medanalytics.com> >>>>> on Thu, 03 Apr 2003 09:24:20 -0600 writes: Marc> Martin, Marc> Not sure if you are aware of this, but since yesterday Marc> there seems to be multi-hour delays in outbound e-mail Marc> from r-help and r-devel. Inbound mail seems to show Marc> up

>>>>> "Marc" == Marc Schwartz <mschwartz@medanalytics.com> >>>>> on Thu, 03 Apr 2003 09:24:20 -0600 writes: Marc> Martin, Marc> Not sure if you are aware of this, but since yesterday Marc> there seems to be multi-hour delays in outbound e-mail Marc> from r-help and r-devel. Inbound mail seems to show Marc> up

Hello there, I've just noticed that scripts in /etc/cron.{daily,weekly,...} are not launched for several weeks (I noticed a `locate` not finding a recently added binary). Exactly, it's since June 02, and `# service cron status` says: Redirecting to /bin/systemctl status crond.service * crond.service - Command Scheduler Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled;

passwd: Authentication token manipulation error smbpasswd: machine 127.0.0.1 rejected the password change: Error was : Wrong Password best regards [FACILITY/btombul at samba ~]$ passwd Changing password for user FACILITY/btombul. Changing password for FACILITY/btombul (current) NT password: New password: Retype new password: passwd: Authentication token manipulation error [FACILITY/btombul at

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

I have a script I put in /etc/cron.fiveminutes graphs.sh #!/bin/sh env LANG=C mrtg /home/admin/domains/my---server.com/public_html/traffic/load/mrtg.cfg --logging /dev/null >/dev/null 2>&1 env LANG=C mrtg /home/admin/domains/my---server.com/public_html/traffic/eth0/mrtg.cfg --logging /dev/null >/dev/null 2>&1 #exit 0; Problem is there is some bug that raises an error even

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.