similar to: how to set term environment for cronjobs?

I just launched my first ROR app and i need to implement the session database cleanup. I am new to cronjobs. I have used one once but it was all copy/paste. I was hoping someone knew of a good tutorial or resource to get started here or might be able to give me a little help. I have seen a lot of posts that reference setting a cron job to clear old sessions but I am not clear on: Can you

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

On Tue, Oct 13, 2015 at 02:05:47PM +0000, Richard wrote: > > > >> If not triggered, you might want to show your crontab entries. > > > > I haven't entries in conrtab's users file at this moment, but I > > have done a test: * * * * * ls -la, and it is not triggered. But > > like I say before, installed system cronjobs like logwatch task > >

On 10/13/2015 04:44 PM, zep wrote: > > > On 10/13/2015 09:54 AM, C. L. Martinez wrote: >> I haven't entries in conrtab's users file at this moment, but I have >> done a test: * * * * * ls -la, and it is not triggered. But like I say >> before, installed system cronjobs like logwatch task are not triggered >> ...

Because systemwide cronjobs are installed in /etc/cron.* directories, not in root user cron file.. Eero 11.10.2015 7.39 ip. "C. L. Martinez" <carlopmart at gmail.com> kirjoitti: > On Sunday, October 11, 2015, Jonathan Billings <billings at negate.org> > wrote: > > > On Oct 11, 2015, at 8:20 AM, C. L. Martinez <carlopmart at gmail.com > >

On Tue, Oct 13, 2015 at 1:39 PM, Jonathan Billings <billings at negate.org> wrote: > On Tue, Oct 13, 2015 at 06:24:19AM +0000, C. L. Martinez wrote: >> For example: logwatch. Logwatch sends a daily email report about >> system's health. I didn't received this email from October 9th ... and >> email configuration is ok. > > So your problem is that cron jobs

> 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, October 13, 2015 13:41:56 +0000 >>> From: "C. L. Martinez" <carlopmart at gmail.com> >>>

> 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, October 13, 2015 13:41:56 +0000 >>> From: "C. L. Martinez" <carlopmart at gmail.com> >>>

On 10/13/2015 09:54 AM, C. L. Martinez wrote: > I haven't entries in conrtab's users file at this moment, but I have > done a test: * * * * * ls -la, and it is not triggered. But like I say > before, installed system cronjobs like logwatch task are not triggered > ... _______________________________________________ CentOS mailing > list CentOS at centos.org

zep wrote: > On 10/13/2015 09:54 AM, C. L. Martinez wrote: >> I haven't entries in conrtab's users file at this moment, but I have >> done a test: * * * * * ls -la, and it is not triggered. But like I say >> before, installed system cronjobs like logwatch task are not triggered > > I'd say that crontab doesn't actually prove that the job isn't being

On Sunday, October 11, 2015, Jonathan Billings <billings at negate.org> wrote: > On Oct 11, 2015, at 8:20 AM, C. L. Martinez <carlopmart at gmail.com > <javascript:;>> wrote: > > I am having strange problems with my cron jobs in my CentOS7 kvm > > host. After the initial install and first boot, any cron job > > configured had run (including cron tasks

Hi, How do i check and see errors for cron.daily? My logrotate and logwatch is not running at the specific time daily. Thanks

On Oct 11, 2015, at 8:20 AM, C. L. Martinez <carlopmart at gmail.com> wrote: > I am having strange problems with my cron jobs in my CentOS7 kvm > host. After the initial install and first boot, any cron job > configured had run (including cron tasks installed by some rpm > packages). Did you have a question or error to point out? So far all I see is a correctly-running system.

On 10/11/2015 09:38 AM, C. L. Martinez wrote: > That's the problem. There is no error but any cron job configured runs.. > And this is the cuestion: why any cron job works?. It's not clear what you're asking. It would help if you replied with an example of a specific job that's configured on your system, and explaining what it is doing that it should not, or what it is

On Mon, Oct 12, 2015 at 12:15 AM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 10/11/2015 09:38 AM, C. L. Martinez wrote: >> >> That's the problem. There is no error but any cron job configured runs.. >> And this is the cuestion: why any cron job works?. > > > It's not clear what you're asking. It would help if you replied with an >

On Tue, Oct 13, 2015 at 06:24:19AM +0000, C. L. Martinez wrote: > For example: logwatch. Logwatch sends a daily email report about > system's health. I didn't received this email from October 9th ... and > email configuration is ok. So your problem is that cron jobs *DO NOT* run? Because every message you've sent so far has said that all jobs run. -- Jonathan Billings

> Date: Tuesday, October 13, 2015 13:41:56 +0000 > From: "C. L. Martinez" <carlopmart at gmail.com> > > > On Tue, Oct 13, 2015 at 1:39 PM, Jonathan Billings > <billings at negate.org> wrote: >> On Tue, Oct 13, 2015 at 06:24:19AM +0000, C. L. Martinez wrote: >>> For example: logwatch. Logwatch sends a daily email report about >>>

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 05:33:28 UTC; 8h ago > Main PID: 607 (crond) > CGroup: /system.slice/crond.service > ??607

On Tue, 13 Oct 2015, C. L. Martinez wrote: > Nop, because binary logs (using journalctl) are disabled in this host > ... But under /var/log/messages, there is no error ... Might it be an idea to *not* disable logging? jh

On 10/13/2015 07:39 AM, C. L. Martinez wrote: > Nop, because binary logs (using journalctl) are disabled in this host > ... But under /var/log/messages, there is no error ... If you haven't reconfigured rsyslogd to use the uxsock source, disabling the journal will also disable the legacy logging system. If your cron log is actually empty, then you probably aren't getting any logs