On Thu, 25 Mar 2021 08:58:20 -0500
SternData wrote:
> In F33's logwatch, I'm seeing a CRON block full of lines like this:
>
> This seems to be new.
Yep, new:
https://bugzilla.redhat.com/show_bug.cgi?id=1941630
___
users mailing list -- users@lists.fed
On Fri, 31 Jul 2020 05:51:21 +0800
Ed Greshko wrote:
> Well, it seems similar issues have come up in the past.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1309108
>
> and
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1298192
>
> You may want to try the work around in comment 19 of that
On 2020-07-31 01:25, stan via users wrote:
> On Thu, 30 Jul 2020 05:09:30 +0800
> Ed Greshko wrote:
>
>> Have you considered doing a relabel?
>>
>> fixfiles -F onboot
>>
>> and reboot?
> I tried a touch /.autorelabel and reboot but it followed symbolic links,
> and I have a bunch of links in /home
On Thu, 30 Jul 2020 05:09:30 +0800
Ed Greshko wrote:
> Have you considered doing a relabel?
>
> fixfiles -F onboot
>
> and reboot?
I tried a touch /.autorelabel and reboot but it followed symbolic links,
and I have a bunch of links in /home and /mnt. So I stopped it. It
looks like I can rest
On 2020-07-30 04:29, stan via users wrote:
> I reinstalled all the selinux components, and still the problem
> persists. I'm going to drop this for a while, see if anything comes to
> me. I have your workaround for the time being.
Have you considered doing a relabel?
fixfiles -F onboot
and reb
On Thu, 30 Jul 2020 02:47:22 +0800
Ed Greshko wrote:
>
> In the above, is PID 5954 the crond process? If you run ps with the
> -Z option do you get something like
>
> [egreshko@f31k ~]$ ps p 821 -Z
> LABEL PID TTY STAT TIME COMMAND
> system_u:system_r:crond
On 2020-07-29 23:25, stan via users wrote:
> On Wed, 29 Jul 2020 20:54:38 +0800
> Ed Greshko wrote:
>
>> So, dwatch is not part of Fedora.
> Not now.
Right. It was retired around F24 and you've rebuilt it locally to make a F31
package.
>> Well, you should easily be able to tell if the hourly c
On Wed, 29 Jul 2020 20:54:38 +0800
Ed Greshko wrote:
> So, dwatch is not part of Fedora.
Not now.
> On an F31 system...
>
> [egreshko@f31k ~]$ dnf info dwatch
> Last metadata expiration check: 0:00:33 ago on Wed 29 Jul 2020
> 08:49:46 PM CST. Error: No matching Packages to list
>
> On an F32
On 2020-07-29 20:29, stan via users wrote:
> On Wed, 29 Jul 2020 05:38:29 +0800
> Ed Greshko wrote:
>
>> On 2020-07-29 03:23, stan via users wrote:
>>> On Tue, 28 Jul 2020 10:35:54 -0700
>>> stan via users wrote:
>>>
Before I open a bugzilla, I wanted to check if anyone has an
explana
On Wed, 29 Jul 2020 05:38:29 +0800
Ed Greshko wrote:
> On 2020-07-29 03:23, stan via users wrote:
> > On Tue, 28 Jul 2020 10:35:54 -0700
> > stan via users wrote:
> >
> >> Before I open a bugzilla, I wanted to check if anyone has an
> >> explanation for this, and a fix.
> > Opened a bugzilla
On 2020-07-29 03:23, stan via users wrote:
> On Tue, 28 Jul 2020 10:35:54 -0700
> stan via users wrote:
>
>> Before I open a bugzilla, I wanted to check if anyone has an
>> explanation for this, and a fix.
> Opened a bugzilla,
> https://bugzilla.redhat.com/show_bug.cgi?id=1861505
Could you clarif
On Tue, 28 Jul 2020 10:35:54 -0700
stan via users wrote:
> Before I open a bugzilla, I wanted to check if anyone has an
> explanation for this, and a fix.
Opened a bugzilla,
https://bugzilla.redhat.com/show_bug.cgi?id=1861505
___
users mailing list --
On Tue, 28 Jul 2020 11:53:15 -0700
Samuel Sieb wrote:
> On 7/28/20 10:35 AM, stan via users wrote:
> > Recently, I've noticed that some jobs that are started by dwatch,
> > aren't starting. If I start them manually, they start fine.
> > dwatch is
>
> What is "dwatch". I can't find any refere
On 7/28/20 10:35 AM, stan via users wrote:
Recently, I've noticed that some jobs that are started by dwatch,
aren't starting. If I start them manually, they start fine. dwatch is
What is "dwatch". I can't find any reference to it (other than BSD).
On 7/28/20 10:35 AM, stan via users wrote:
Recently, I've noticed that some jobs that are started by dwatch,
aren't starting. If I start them manually, they start fine. dwatch is
in cron.d, and should be running every 5 minutes, but no cron jobs are
running. I see the following in journalctl,
On 09/04/2020 12:24, Ed Greshko wrote:
On 2020-04-09 17:57, Terry Barnaby wrote:
The script already has date/time and the log shows (The Wed 8th entries entry
having the PID):
Bbackup / /usr/beam /home /src /srcOld /dist /opt /scratch /data/svn /data/www
/data/vwt /data/www /data1/kvm /data/d
On 2020-04-09 17:57, Terry Barnaby wrote:
> The script already has date/time and the log shows (The Wed 8th entries entry
> having the PID):
>
> Bbackup / /usr/beam /home /src /srcOld /dist /opt /scratch /data/svn
> /data/www /data/vwt /data/www /data1/kvm /data/database /data/vwt
> /data/backup
On 09/04/2020 07:00, francis.montag...@inria.fr wrote:
Hi
On Tue, 07 Apr 2020 07:07:36 +0100 Terry Barnaby wrote:
# Min Hour Day Month WeekDay
# Perform incremental backup to every work day
01 23 * * 1 root /src/bbackup/bbackup-beam
01 23 * * 2 root /src/bbackup/bbackup-beam
01 23 * * 3 root /
On 08/04/2020 23:11, Cameron Simpson wrote:
On 08Apr2020 14:54, Terry Barnaby wrote:
Note this has happened a few times this year, (approx 1 in 64 x) so
not related to DST changes anyway. Might be due to chrony clock
resyncs I suppose but I think something stranger is going on here or
somethi
Hi
On Tue, 07 Apr 2020 07:07:36 +0100 Terry Barnaby wrote:
> # Min Hour Day Month WeekDay
> # Perform incremental backup to every work day
> 01 23 * * 1 root /src/bbackup/bbackup-beam
> 01 23 * * 2 root /src/bbackup/bbackup-beam
> 01 23 * * 3 root /src/bbackup/bbackup-beam
> 01 23 * * 4 root /s
On 08Apr2020 14:54, Terry Barnaby wrote:
Note this has happened a few times this year, (approx 1 in 64 x) so not
related to DST changes anyway. Might be due to chrony clock resyncs I
suppose but I think something stranger is going on here or something
silly and obvious in what I am doing.
I
On 08Apr2020 07:52, Ed Greshko wrote:
On 2020-04-08 07:27, Cameron Simpson wrote:
On 07Apr2020 07:07, Terry Barnaby wrote:
01 23 * * 1 root /src/bbackup/bbackup-beam
[...]
1:23am. Do not the timezone shifts happen at 2am (avoids horrible day changes
if it happened at 12am). So 1:23am can h
On 04/08/2020 06:21 AM, Patrick O'Callaghan wrote:
I don't know how it works where you live, but in the UK the autumn
switch occurs at 2am, which reverts back to being 1am. Thus a time such
as 1:30am occurs twice, and events programmed for that time can be
triggered twice.
It's the same in the
On 2020-04-08 21:37, Patrick O'Callaghan wrote:
> On Wed, 2020-04-08 at 20:28 +0800, Ed Greshko wrote:
>>> I don't know how it works where you live, but in the UK the autumn
>>> switch occurs at 2am, which reverts back to being 1am. Thus a time such
>>> as 1:30am occurs twice, and events programmed
On 08/04/2020 14:37, Patrick O'Callaghan wrote:
On Wed, 2020-04-08 at 20:28 +0800, Ed Greshko wrote:
I don't know how it works where you live, but in the UK the autumn
switch occurs at 2am, which reverts back to being 1am. Thus a time such
as 1:30am occurs twice, and events programmed for that t
On Wed, 2020-04-08 at 20:28 +0800, Ed Greshko wrote:
> > I don't know how it works where you live, but in the UK the autumn
> > switch occurs at 2am, which reverts back to being 1am. Thus a time such
> > as 1:30am occurs twice, and events programmed for that time can be
> > triggered twice.
> >
>
On 2020-04-08 20:21, Patrick O'Callaghan wrote:
> On Wed, 2020-04-08 at 17:06 +0800, Ed Greshko wrote:
>> On 2020-04-08 16:56, Patrick O'Callaghan wrote:
>>> On Wed, 2020-04-08 at 07:52 +0800, Ed Greshko wrote:
On 2020-04-08 07:27, Cameron Simpson wrote:
> On 07Apr2020 07:07, Terry Barnaby
On Wed, 2020-04-08 at 20:11 +0800, Ed Greshko wrote:
>If time was adjusted one hour forward, those jobs that would have run
> in
>the interval that has been skipped will be run immediately.
> Conversely,
>if time was adjusted backward, running the same job twice is avoide
On Wed, 2020-04-08 at 17:06 +0800, Ed Greshko wrote:
> On 2020-04-08 16:56, Patrick O'Callaghan wrote:
> > On Wed, 2020-04-08 at 07:52 +0800, Ed Greshko wrote:
> > > On 2020-04-08 07:27, Cameron Simpson wrote:
> > > > On 07Apr2020 07:07, Terry Barnaby wrote:
> > > > > 01 23 * * 1 root /src/bbackup
On 2020-04-08 20:01, Andy Paterson via users wrote:
> I understood crontab used UTC time - daylight saving shouldn't apply
>
Not unless you set the CRON_TZ variable.
Also, if that were the case then the man page wouldn't need to tell you
Daylight Saving Time and other time changes
I understood crontab used UTC time - daylight saving shouldn't apply
> On 8 Apr 2020, at 10:07, Ed Greshko wrote:
>
> On 2020-04-08 16:56, Patrick O'Callaghan wrote:
>>> On Wed, 2020-04-08 at 07:52 +0800, Ed Greshko wrote:
>>> On 2020-04-08 07:27, Cameron Simpson wrote:
On 07Apr2020 07:07,
On 2020-04-08 16:56, Patrick O'Callaghan wrote:
> On Wed, 2020-04-08 at 07:52 +0800, Ed Greshko wrote:
>> On 2020-04-08 07:27, Cameron Simpson wrote:
>>> On 07Apr2020 07:07, Terry Barnaby wrote:
01 23 * * 1 root /src/bbackup/bbackup-beam
>>> [...]
>>>
>>> 1:23am. Do not the timezone shifts ha
On Wed, 2020-04-08 at 07:52 +0800, Ed Greshko wrote:
> On 2020-04-08 07:27, Cameron Simpson wrote:
> > On 07Apr2020 07:07, Terry Barnaby wrote:
> > > 01 23 * * 1 root /src/bbackup/bbackup-beam
> > [...]
> >
> > 1:23am. Do not the timezone shifts happen at 2am (avoids horrible day
> > changes if
On 2020-04-08 07:27, Cameron Simpson wrote:
> On 07Apr2020 07:07, Terry Barnaby wrote:
>> 01 23 * * 1 root /src/bbackup/bbackup-beam
> [...]
>
> 1:23am. Do not the timezone shifts happen at 2am (avoids horrible day changes
> if it happened at 12am). So 1:23am can happen twice if 2am steps back to
On 07Apr2020 07:07, Terry Barnaby wrote:
01 23 * * 1 root /src/bbackup/bbackup-beam
[...]
1:23am. Do not the timezone shifts happen at 2am (avoids horrible day
changes if it happened at 12am). So 1:23am can happen twice if 2am steps
back to 1am.
Our summer time just ended here. Might a sim
On 4/7/20 3:21 AM, Terry Barnaby wrote:
On 07/04/2020 09:03, Samuel Sieb wrote:
On 4/6/20 11:07 PM, Terry Barnaby wrote:
This system has been in use for 10 years or more on various Fedora
versions. However about 18 months ago I have seen a problem where
cron will start two backups with identic
On 07/04/2020 13:06, Iosif Fettich wrote:
Hi Terry,
Yes, there is nothing unusual in /var/log/cron:
Apr 6 22:01:01 beam CROND[651585]: (root) CMD (run-parts
/etc/cron.hourly)
[...]
/var/log/messages
Feb 24 23:00:03 beam dhcpd[1743]: DHCPREQUEST for 192.168.201.214
from 00:25:b3:e6:a9:18
Hi Terry,
Yes, there is nothing unusual in /var/log/cron:
Apr 6 22:01:01 beam CROND[651585]: (root) CMD (run-parts /etc/cron.hourly)
[...]
/var/log/messages
Feb 24 23:00:03 beam dhcpd[1743]: DHCPREQUEST for 192.168.201.214 from
00:25:b3:e6:a9:18 via enp4s0
[...]
In the backup log:
Bba
Hi Terry,
The bbackup-beam shell script is pretty basic and I can't see how this could
have an issue like this.
Googling on similar issues finds some hits where the cause were two
running cron daemons, e.g.
https://stackoverflow.com/questions/1004764/why-is-this-cron-entry-executed-twice
I
Hi Terry,
I have assumed the system time is always UTC synchronised using chronyd. The
servers user code is running under the GMT timezone. I was wondering if the
tweaking of the time by chronyd could cause this issue, but I would have
thought this situation would have been handled by crond
On 07/04/2020 09:03, Samuel Sieb wrote:
On 4/6/20 11:07 PM, Terry Barnaby wrote:
This system has been in use for 10 years or more on various Fedora
versions. However about 18 months ago I have seen a problem where
cron will start two backups with identical start times occasionally.
I have had
On 07/04/2020 09:25, Iosif Fettich wrote:
Hi,
On 2020-04-07 14:07, Terry Barnaby wrote:
I have a simple backup system that starts off a backup once per
night during the weekdays. There is a crontab file in /etc/cron.d
with the following entries:
#
Hi,
On 2020-04-07 14:07, Terry Barnaby wrote:
I have a simple backup system that starts off a backup once per night during
the weekdays. There is a crontab file in /etc/cron.d with the following entries:
# Beam B
On 4/6/20 11:07 PM, Terry Barnaby wrote:
This system has been in use for 10 years or more on various Fedora
versions. However about 18 months ago I have seen a problem where cron
will start two backups with identical start times occasionally.
I have had to add a file lock system in the bbackup
On 07/04/2020 08:21, Ed Greshko wrote:
On 2020-04-07 14:07, Terry Barnaby wrote:
I have a simple backup system that starts off a backup once per night during
the weekdays. There is a crontab file in /etc/cron.d with the following entries:
###
On Tue, 2020-04-07 at 07:07 +0100, Terry Barnaby wrote:
> I have had to add a file lock system in the bbackup-beam to cope with
> this.
Probably a good thing to do, anyway.
--
uname -rsvp
Linux 3.10.0-1062.18.1.el7.x86_64 #1 SMP Tue Mar 17 23:49:17 UTC 2020 x86_64
Boilerplate: All unexpect
On 2020-04-07 14:07, Terry Barnaby wrote:
> I have a simple backup system that starts off a backup once per night during
> the weekdays. There is a crontab file in /etc/cron.d with the following
> entries:
>
>
> # Be
On 09/24/2016 12:02 PM, Patrick Dupre wrote:
You mention 3 files in
/usr/share/anacron
there are in /var/spool/anacron
in my machine
I am not sure that they control anything, maybe they monitor.
Those are the timestamp files mentioned in the man page. They tell the
program when it was last r
"Jon LaBadie"
> To: users@lists.fedoraproject.org
> Subject: Re: cron
>
> On Sat, Sep 24, 2016 at 10:05:36AM +0200, Patrick Dupre wrote:
> > Hello,
> >
> > It seems that we are experiencing different behaviours.
> > It there any test that we could run
On Sat, Sep 24, 2016 at 10:05:36AM +0200, Patrick Dupre wrote:
> Hello,
>
> It seems that we are experiencing different behaviours.
> It there any test that we could run to try to identify where the
> glitch is ?
>
> By the way, nobody told me how to control anacron.
> The installation day can no
On 09/24/2016 01:05 AM, Patrick Dupre wrote:
By the way, nobody told me how to control anacron.
The installation day can no be considered as a normal way to
control an application !
The first thing you should always do is RTFM. In this case:
man anacron
man anacrontab
___
=
> Sent: Friday, September 23, 2016 at 11:49 PM
> From: "Jon LaBadie"
> To: users@lists.fedoraproject.org
> Subject: Re: cron
>
> On Fri, Sep 23, 2016 at 09:23:43PM +0200, Patrick Dupre wrote:
> > > From: "Jon LaBadie"
> >
On Fri, 23 Sep 2016 17:49:34 -0400
Jon LaBadie wrote:
> Please consider that your F24 setup is incomplete or has some
> errors and your experience is not the norm.
It works fine for me with everything moved into cron.
Here's my /etc/crontab:
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MA
On Fri, Sep 23, 2016 at 09:23:43PM +0200, Patrick Dupre wrote:
> > From: "Jon LaBadie"
> > On Fri, Sep 23, 2016 at 01:32:00PM +0200, Patrick Dupre wrote:
> > >
> > > > Regardless, as has been said before, if you want a job run at
> > > > specific times, anacron is not the correct tool. Use cron.
On Fri, Sep 23, 2016 at 09:23:43PM +0200, Patrick Dupre wrote:
> In fc22, anacron and crond where both running simultaneously fine.
> No any more in fc24 : it seems that now crond only run hourly
> and ignore the weekly (and daily) tasks. That I wish to
> restablish.
Do you have cronie-anacron i
Dunkerque, France
===
> Sent: Friday, September 23, 2016 at 8:10 PM
> From: "Jon LaBadie"
> To: users@lists.fedoraproject.org
> Subject: Re: cron
>
> On Fri, Sep 23, 2016 at 01:32:00PM +0200, Patr
On Fri, Sep 23, 2016 at 01:32:00PM +0200, Patrick Dupre wrote:
>
> > Regardless, as has been said before, if you want a job run at
> > specific times, anacron is not the correct tool. Use cron.
> >
> Yes and no,
> Monday is not a good day. I would like to move to Saturday
> Why not a START_DAYS_
doraproject.org
> Subject: Re: cron
>
> On Fri, Sep 23, 2016 at 09:52:30AM +0200, Patrick Dupre wrote:
> >
> > > From: "Jon LaBadie"
> > > To: users@lists.fedoraproject.org
> > > Subject: Re: cron
> > >
> > > On Thu, Sep 22, 2016
On Fri, Sep 23, 2016 at 09:52:30AM +0200, Patrick Dupre wrote:
>
> > From: "Jon LaBadie"
> > To: users@lists.fedoraproject.org
> > Subject: Re: cron
> >
> > On Thu, Sep 22, 2016 at 06:56:07PM -0400, Tom Horsley wrote:
> > > On Thu,
8 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===
> Sent: Friday, September 23, 2016 at 2:13 AM
> From: "Jon LaBadie"
> To: users@lists.fe
On Thu, Sep 22, 2016 at 06:56:07PM -0400, Tom Horsley wrote:
> On Thu, 22 Sep 2016 23:56:04 +0200
> Patrick Dupre wrote:
>
> > anacron weakly is supposed to run on saturday, it run on Monday now !
> > Same thing for cron !
>
> There is no "supposed to" with anacron. It decides when to run
> stuf
On Thu, 22 Sep 2016 23:56:04 +0200
Patrick Dupre wrote:
> anacron weakly is supposed to run on saturday, it run on Monday now !
> Same thing for cron !
There is no "supposed to" with anacron. It decides when to run
stuff for it's own wacky reasons. Did you install f24 on
a Monday? It may have de
8 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===
> Sent: Thursday, September 22, 2016 at 7:14 AM
> From: "Jon LaBadie"
> To: users@lists.fe
On Wed, Sep 21, 2016 at 07:26:18PM +0200, Patrick Dupre wrote:
> Hello,
>
> I am a bit surprise by the answers that I received.
> Again, cron and anacron used to run quite well for a long time.
> Both can co-live, one run periodically according to /etc/crontab
> and /etc/cron.daily /etc/cron.weekl
On Wed, 21 Sep 2016 11:30:49 -0700
Rick Stevens wrote:
> You do know you can modify the "START_HOURS_RANGE=" parameter in
> /etc/anacrontab to tell anacron when it is permitted to run things,
> right?
Yep. I also know I can completely eradicate anacron :-).
>If you want to disable anacron but le
On 09/21/2016 10:45 AM, Tom Horsley wrote:
> On Wed, 21 Sep 2016 19:26:18 +0200
> Patrick Dupre wrote:
>
>> Why give up this logic?
>
> Because my machine is never turned off, and anacron has the
> uncanny ability to make things run at the most inconvenient possible
> times to interfere with thin
Horsley"
> To: users@lists.fedoraproject.org
> Subject: Re: cron
>
> On Wed, 21 Sep 2016 19:26:18 +0200
> Patrick Dupre wrote:
>
> > Why give up this logic?
>
> Because my machine is never turned off, and anacron has the
> uncanny ability to make things run at the most
On Wed, 21 Sep 2016 19:26:18 +0200
Patrick Dupre wrote:
> Why give up this logic?
Because my machine is never turned off, and anacron has the
uncanny ability to make things run at the most inconvenient possible
times to interfere with things I'm trying to do.
Cron runs thing when I want them to
ue, France
===
> Sent: Wednesday, September 21, 2016 at 6:27 PM
> From: "Tom Horsley"
> To: users@lists.fedoraproject.org
> Subject: Re: cron
>
> On Wed, 21 Sep 2016 10:26:14 -0400
> Matthew Miller wrote:
>
> &
On Wed, 21 Sep 2016 10:26:14 -0400
Matthew Miller wrote:
> If you care about the *particular* time that a job runs, rather than
> just wanting to make sure it gets run once in a certain period,
> cron.daily and cron.weekly are not for you. Instead, drop a file in
> /etc/cron.d with the traditional
On Wed, Sep 21, 2016 at 10:02:19AM +0200, Patrick Dupre wrote:
> and in my /etc/anacrontab
> 1 5 cron.daily nice run-parts /etc/cron.daily
> 7 25 cron.weekly nice run-parts /etc/cron.weekly
>
> but
>
> anacron is executed on the Monday !
> N 44 Mond
| | 59140 Dunkerque, France
===
> Sent: Wednesday, September 21, 2016 at 1:17 AM
> From: "Samuel Sieb"
> To: "Community support for Fedora users"
> Subject: Re: cron
>
> On 09/20/2016 03:52
On 09/20/2016 04:17 PM, Samuel Sieb wrote:
> On 09/20/2016 03:52 PM, Patrick Dupre wrote:
>> Finally, I still do not know how to manage the schedule for cron.weekly
>> and cron.daily, since /etc/anacrontab or /etc/crontab are just ignored
>> in fc24.
>>
> Why do you think that? My cron.weekly and
On 09/20/2016 03:52 PM, Patrick Dupre wrote:
Finally, I still do not know how to manage the schedule for cron.weekly
and cron.daily, since /etc/anacrontab or /etc/crontab are just ignored
in fc24.
Why do you think that? My cron.weekly and cron.daily get run and they
are referenced from /etc/an
On 07/14/2016 08:55 AM, bruce wrote:
Jul 14 08:45:09 crawl1 abrt: detected unhandled Python exception in
'/crawl_tmp/jcccParse_cloud_test.py'
Jul 14 08:45:09 crawl1 abrtd: Directory
'pyhook-2016-07-14-08:45:09-14939' creation detected
Jul 14 08:45:09 crawl1 abrt-server[14944]: Saved Python crash
On 21Nov2014 19:22, Mike Chambers wrote:
I have a couple of cron jobs setup in my /etc/cron.d/ dir and they seem
to be checked and run as suppose to, according to /var/log/cron.
Basically the 2 jobs point to a couple of dir's that run a few scripts
every so few hours and mirror a few things from
5 */4 * * * root run-parts /etc/cron.quarterly | mailx -s "test"
??
hth,jackc...
On Fri, Nov 21, 2014 at 5:22 PM, Mike Chambers wrote:
> Hi all,
>
> I have a couple of cron jobs setup in my /etc/cron.d/ dir and they seem
> to be checked and run as suppose to, according to /var/log/cron.
> B
On 18Dec2013 00:43, Jonathan Ryshpan wrote:
> * Frequently, I start the system, check my email and leave for
> breakfast; on these days, I'd like backup to start when I leave;
> I would invoke it by a shell script or whatever.
> * Other days, I stay on the system for a
Jonathan Ryshpan writes:
> In more detail: I have a cron job which backs up my desktop system
> every day. The job is actually invoked by anacron, which starts it
> about an hour after I boot up the system for the day. Backing up takes
> from half an hour to an hour and a half, depending.
>
> *
On 12/18/2013 12:43 AM, Jonathan Ryshpan wrote:
*
If I can replace /cron/ with /at/ and get the desired result, I'll be happy.
You may want to consider using batch instead, running the command as
part of setting up your login session. This will start the backup when
the load average drops b
On Wed, 2013-12-18 at 00:52 +, Patrick O'Callaghan wrote:
> On Tue, Dec 17, 2013 at 7:23 PM, Jonathan Ryshpan
> wrote:
>
> I'm interested in a replacement for cron which would allow me
> to run various cron jobs on demand, and mark them as having
> been run, so they wo
On Tue, Dec 17, 2013 at 7:23 PM, Jonathan Ryshpan wrote:
> I'm interested in a replacement for cron which would allow me to run
> various cron jobs on demand, and mark them as having been run, so they
> won't be run again from the schedule. Looking through the Fedora
> repository, I noticed whenj
On 03.10.2013 23:38, Ranjan Maitra wrote:
>
> Following, this post pointed to me my Matthew Miller, I am able to get
> things working. Here is what I did (same as in the post there).
>
> Created a file as follows (called ~/bin/export_x_info):
>
> #!/bin/bash
> # Export the dbus session address
On Thu, Oct 03, 2013 at 03:00:55PM -0700, Joe Zeff wrote:
> >touch $HOME/.Xdbus
> >chmod 600 $HOME/.Xdbus
> >env | grep DBUS_SESSION_BUS_ADDRESS > $HOME/.Xdbus
> >echo 'export DBUS_SESSION_BUS_ADDRESS' >> $HOME/.Xdbus
> ># Export XAUTHORITY value on startup so it can be used by cron
> >env | grep X
On Thu, 3 Oct 2013 15:00:55 -0700 Joe Zeff wrote:
> On 10/03/2013 02:38 PM, Ranjan Maitra wrote:
> > #!/bin/bash
> > # Export the dbus session address on startup so it can be used by cron
> > touch $HOME/.Xdbus
> > chmod 600 $HOME/.Xdbus
> > env | grep DBUS_SESSION_BUS_ADDRESS > $HOME/.Xdbus
> >
On 10/03/2013 02:38 PM, Ranjan Maitra wrote:
#!/bin/bash
# Export the dbus session address on startup so it can be used by cron
touch $HOME/.Xdbus
chmod 600 $HOME/.Xdbus
env | grep DBUS_SESSION_BUS_ADDRESS > $HOME/.Xdbus
echo 'export DBUS_SESSION_BUS_ADDRESS' >> $HOME/.Xdbus
# Export XAUTHORITY v
On Wed, 2 Oct 2013 21:38:26 -0400 Matthew Miller
wrote:
> On Wed, Oct 02, 2013 at 07:55:51PM -0500, Ranjan Maitra wrote:
> > 0 * * * * maitra DISPLAY=:0.0 $HOME/scripts/yum/check-kernel.sh
>
> Did you try the things in the blog post I'd linked to? As I said in my
> previous method, notify-send n
Is the script executable?
-b
On 10/02/2013 05:10 PM, Ranjan Maitra wrote:
Hi,
I have a cron job running which yum updates all my machines once a day.
All of these work fine.
I also have a cron job which checks for kernel updates every hour and
sends me a message if an updated kernel has been
On 03.10.2013 02:55, Ranjan Maitra wrote:
>
> Thanks! But this does not "work" either. Here is what I tried in my
> crontab -e:
>
> 0 * * * * maitra DISPLAY=:0.0 $HOME/scripts/yum/check-kernel.sh
>
> (maitra is my username).
>
> Here is how I changed my check-kernel.sh, though I am not sure if
On Wed, Oct 2, 2013 at 10:42 PM, Ranjan Maitra
wrote:
> On Wed, 2 Oct 2013 20:53:52 -0500 inode0 wrote:
>
>> On Wed, Oct 2, 2013 at 10:10 AM, Ranjan Maitra
>> wrote:
>> > Hi,
>> >
>> > I have a cron job running which yum updates all my machines once a day.
>> > All of these work fine.
>> >
>> >
On Wed, 2 Oct 2013 20:53:52 -0500 inode0 wrote:
> On Wed, Oct 2, 2013 at 10:10 AM, Ranjan Maitra
> wrote:
> > Hi,
> >
> > I have a cron job running which yum updates all my machines once a day.
> > All of these work fine.
> >
> > I also have a cron job which checks for kernel updates every hour
On Wed, 2 Oct 2013 21:38:26 -0400 Matthew Miller
wrote:
> On Wed, Oct 02, 2013 at 07:55:51PM -0500, Ranjan Maitra wrote:
> > 0 * * * * maitra DISPLAY=:0.0 $HOME/scripts/yum/check-kernel.sh
>
> Did you try the things in the blog post I'd linked to? As I said in my
> previous method, notify-send n
On Wed, 2 Oct 2013 20:53:52 -0500 inode0 wrote:
> On Wed, Oct 2, 2013 at 10:10 AM, Ranjan Maitra
> wrote:
> > Hi,
> >
> > I have a cron job running which yum updates all my machines once a day.
> > All of these work fine.
> >
> > I also have a cron job which checks for kernel updates every hour
On Wed, Oct 2, 2013 at 10:10 AM, Ranjan Maitra
wrote:
> Hi,
>
> I have a cron job running which yum updates all my machines once a day.
> All of these work fine.
>
> I also have a cron job which checks for kernel updates every hour and
> sends me a message if an updated kernel has been installed.
On 10/02/2013 05:55 PM, Ranjan Maitra wrote:
Thanks! But this does not "work" either.
There may be a much easier way: before your cron job starts the update,
have it do this:
yum check-update > /tmp/updates.txt
Then, after the update, grep /tmp/updates.txt looking for kernel,
redirecting t
On Wed, Oct 02, 2013 at 07:55:51PM -0500, Ranjan Maitra wrote:
> 0 * * * * maitra DISPLAY=:0.0 $HOME/scripts/yum/check-kernel.sh
Did you try the things in the blog post I'd linked to? As I said in my
previous method, notify-send needs to talk to your dbus session, and it
can't get that from inside
On Thu, 3 Oct 2013 02:17:09 +0200 poma
wrote:
> On 02.10.2013 22:06, Ranjan Maitra wrote:
> …
> > However, what I do not understand is why this does not "work" though. I
> > do not understand because notify-send is in /usr/bin as well as in /bin:
> >
> > $ which notify-send
> > notify-send is
On 02.10.2013 22:06, Ranjan Maitra wrote:
…
> However, what I do not understand is why this does not "work" though. I
> do not understand because notify-send is in /usr/bin as well as in /bin:
>
> $ which notify-send
> notify-send is /bin/notify-send
> notify-send is /usr/bin/notify-send
>
> Bot
On 10/02/2013 02:27 PM, Ranjan Maitra issued this missive:
On Wed, 2 Oct 2013 13:34:36 -0700 Rick Stevens
wrote:
On 10/02/2013 01:06 PM, Ranjan Maitra issued this missive:
On Wed, 2 Oct 2013 09:26:32 -0700 Rick Stevens
wrote:
On 10/02/2013 08:10 AM, Ranjan Maitra issued this missive:
Hi,
On Wed, 2 Oct 2013 13:34:36 -0700 Rick Stevens
wrote:
> On 10/02/2013 01:06 PM, Ranjan Maitra issued this missive:
> > On Wed, 2 Oct 2013 09:26:32 -0700 Rick Stevens
> > wrote:
> >
> >> On 10/02/2013 08:10 AM, Ranjan Maitra issued this missive:
> >>> Hi,
> >>>
> >>> I have a cron job running whi
1 - 100 of 113 matches
Mail list logo
