On Fri, 2024-07-19 at 10:51 +0700, Frederic Muller wrote:
> So it runs daily, allow for a delay when starting and supposidely
> checks
> whether the job has been executed... seems like what I was looking
> for no?
I'd look into what that actually means. Does it just check that the job
was started
great.
However wanting to do that daily automatically from my laptop to a
local
network drive I looked for a way to start the backup like 10 minutes
after I switched on the PC and only once a day which led me to
anacron.
Installed it, set up the anacron job and the problems arrived.
Initially
tried to r
> that:
> > very easy to setup and works great.
> >
> > However wanting to do that daily automatically from my laptop to a
> > local
> > network drive I looked for a way to start the backup like 10
> > minutes
> > after I switched on the PC and only
local
network drive I looked for a way to start the backup like 10 minutes
after I switched on the PC and only once a day which led me to anacron.
How about a systemd timer that is fired fired 10 minutes after boot.
Its ExecStart could call a script that checks for a touched file ( a
semaphore
wanting to do that daily automatically from my laptop to a
> local
> network drive I looked for a way to start the backup like 10 minutes
> after I switched on the PC and only once a day which led me to
> anacron.
>
> Installed it, set up the anacron job and the problems arrived.
>
start the backup like 10 minutes
after I switched on the PC and only once a day which led me to anacron.
Installed it, set up the anacron job and the problems arrived. Initially
tried to run it as my user but that didn't work.
@daily 10 daily-backup su fred -c "/home/fred
On Thu, Feb 10, 2022 at 09:41:23PM +0100, Patrick Dupre wrote:
Hello,
Currently anacrontab is set
7 25 cron.weekly nice run-parts /etc/cron.weekly
It means that it run every Thursday.
I am no satisfied by thus day.
How can I have it running every Saturday ?
crontab is no
doesn’t actually set a day of
week, just the interval between runs. It checks a date in
/var/spool/anacron/cron.weekly, and if it has been more than 7 days (that’s
what the 7 stands for in that line) then it runs. Then it sets the date in the
spool file for that day, so subsequent checks will ref
My fix to anacron is to eradicate it and run everything in cron
which doesn't randomize run times :-).
Put back the traditional /etc/crontab and remove the
/etc/cron.hourly/0anacron file, and now cron works the
way it always did.
___
users mailing
On 2/10/22 14:08, Patrick Dupre wrote:
On 2/10/22 13:41, Patrick Dupre wrote:
Currently anacrontab is set
7 25 cron.weekly nice run-parts /etc/cron.weekly
It means that it run every Thursday.
I am no satisfied by thus day.
How can I have it running every Saturday ?
No, t
On 2/10/22 12:41, Patrick Dupre wrote:
How can I have it running every Saturday ?
Change the "last run date" in /var/spool/anacron/cron.weekly.
(For reference: This is indicated by the "FILES" section of the
anacron(8) man page.)
_
On 2/10/22 13:08, Patrick Dupre wrote:
On 2/10/22 13:41, Patrick Dupre wrote:
Currently anacrontab is set
7 25 cron.weekly nice run-parts /etc/cron.weekly
It means that it run every Thursday.
I am no satisfied by thus day.
How can I have it running every Saturday ?
No, t
> On 2/10/22 13:41, Patrick Dupre wrote:
> > Currently anacrontab is set
> > 7 25 cron.weekly nice run-parts /etc/cron.weekly
> >
> > It means that it run every Thursday.
> > I am no satisfied by thus day.
> > How can I have it running every Saturday ?
>
> No, the man page f
On 2/10/22 13:41, Patrick Dupre wrote:
Currently anacrontab is set
7 25 cron.weekly nice run-parts /etc/cron.weekly
It means that it run every Thursday.
I am no satisfied by thus day.
How can I have it running every Saturday ?
No, the man page for /etc/crontab says that
Hello,
Currently anacrontab is set
7 25 cron.weekly nice run-parts /etc/cron.weekly
It means that it run every Thursday.
I am no satisfied by thus day.
How can I have it running every Saturday ?
crontab is not activated
#30 12 * * 6 root run-parts /etc/cron.weekly
6 would
etc/cron.hourly/0anacron that calls anacron. The
anacron job calls cron.daily and cron.weekly from /etc/anacrontab.
That’s why you have two jobs running. They’re both running through cron.daily
and cron.weekly twice.
I suspect either you added those lines at some point or the system had it a
On 11/12/2021 23:48, francis.montag...@inria.fr wrote:
Even easier is to use a systemd service and timer (system or user) to start this
backup: this will do this locking for you.
Needless to say, you are correct. Need to rewire my old-school brain.
--
Did 황준호 die?
On 12/12/2021 02:44, Patrick Dupre wrote:
Thank for all the comments.
Francis Montagnac had the best suggestion.
--
Did 황준호 die?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.o
===
> Sent: Saturday, December 11, 2021 at 5:08 PM
> From: "Jonathan Billings"
> To: "Community support for Fedora users"
> Subject: Re: crond/anacron
>
>
>
> > On Dec 11, 2021, at 10:38, Jonathan
> On Dec 11, 2021, at 10:38, Jonathan Billings wrote:
>
> The thing is, Anacron only runs if you boot after the scheduled job is
> supposed to run out of cron. It shouldn’t run twice. So maybe you have your
> backups scheduled in more than one place?
I should be extra clear
Hi
On Sat, 11 Dec 2021 23:28:20 +0800 Ed Greshko wrote:
> Are you using your own scripts to perform the backups?
> If so, the easy solution would be for the script to check for a "lock file" to
> see if another backup is running. ...
Even easier is to use a systemd service and timer (system or
On Dec 11, 2021, at 09:03, Patrick Dupre wrote:
>
> I am trouble because I guess that crond and anacron
> run are very close times.
> Hence, they start a backup when another backup is running.
> This creates real problems.
>
> What do you recommend?
> Running on
On 11/12/2021 22:02, Patrick Dupre wrote:
I am trouble because I guess that crond and anacron
run are very close times.
Hence, they start a backup when another backup is running.
This creates real problems.
What do you recommend?
Are you using your own scripts to perform the backups?
If so
Hello,
I am trouble because I guess that crond and anacron
run are very close times.
Hence, they start a backup when another backup is running.
This creates real problems.
What do you recommend?
Running only crond or only anacron?
Usually, this machine runs every day for at least 1-2 hours
durin
On Sun, 22 Sep 2019 15:28:06 +0200
Patrick Dupre wrote:
> I only need anacron.
You don't only need anacron, because it only runs when cron
starts it.
Personally, I go to a lot of trouble to eradicate anacron
because I don't want jobs running at random times (which
is utterly ridicu
Thanks.
Every looks fine.
My point is that both anacron and crond run on a weekly basis, while
I only need anacron.
> > On my machine, I have crond and anacron running.
> > I guess that I do not need crond.
> > I can easily manage crond, but waht about anacron?
> >
>
On 9/22/19 6:17 PM, Patrick Dupre wrote:
On my machine, I have crond and anacron running.
I guess that I do not need crond.
I can easily manage crond, but waht about anacron?
systemctl status anacron
Unit anacron.service could not be found
systemctl status anacrond
Unit anacrond.service could
Hello,
On my machine, I have crond and anacron running.
I guess that I do not need crond.
I can easily manage crond, but waht about anacron?
systemctl status anacron
Unit anacron.service could not be found
systemctl status anacrond
Unit anacrond.service could not be found
while
systemctl status
On 3 December 2016 at 12:54, Patrick Dupre wrote:
> Hello,
>
> using anacrontab weekly:
> This is what I have in my anacrontab file:
> 7 15 cron.weekly nice run-parts /etc/cron.weekly
>
> It seems that it run will be run 7 days after the date in
Hello,
using anacrontab weekly:
This is what I have in my anacrontab file:
7 15 cron.weekly nice run-parts /etc/cron.weekly
It seems that it run will be run 7 days after the date in
/var/spool/anacron/cron.weekly
Can I change this date ?
Thank
Allegedly, on or about 17 September 2016, Bob Goodwin sent:
> Is there a command to display only what I want, a specific day or
> perhaps reverse the order so that today's messages are at the top,
> display first? Better yet I would think would be to display them in
> Thunderbird but I don't kno
> Well, lovely. I've found that "systemctl --full list-timers" truncates
> the display if your terminal isn't wide enough (at least it truncates
> using xfce-terminal) and gives you no indication it has done so. Isn't
> "--full" supposed to wrap the display so that doesn't happen? That's
> what th
On 09/19/2016 03:09 PM, Rick Stevens wrote:
Yet another reason I absolutely deplore this systemd/systemctl crap.
Complaining about systemd won't do any good; reporting it as a bug
might, especially if you specify that you're using Xfce instead of Gnome.
___
On Mon, Sep 19, 2016 at 03:09:39PM -0700, Rick Stevens wrote:
>
> Well, lovely. I've found that "systemctl --full list-timers" truncates
> the display if your terminal isn't wide enough (at least it truncates
> using xfce-terminal) and gives you no indication it has done so. Isn't
> "--full" suppo
On Mon, Sep 19, 2016 at 10:57:01PM +0100, Andy Blanchard wrote:
> On 19 September 2016 at 22:38, Patrick Dupre wrote:
> > I did:
> > systemctl enable mlocate-updatedb.service
> > (no error)
> > but it still does not seem to be enabled:
> > ● mlocate-updatedb.service - Update a database for mlocate
On 09/19/2016 02:57 PM, Andy Blanchard wrote:
> On 19 September 2016 at 22:38, Patrick Dupre wrote:
>> I did:
>> systemctl enable mlocate-updatedb.service
>> (no error)
>> but it still does not seem to be enabled:
>> ● mlocate-updatedb.service - Update a database for mlocate
>>Loaded: loaded (
On Mon, 19 Sep 2016 23:19:16 +0200
"Patrick Dupre" wrote:
> OK, Thank.
>
> It was inactive, Then I restart it and now:
> ● mlocate-updatedb.service - Update a database for mlocate
>Loaded: loaded (/usr/lib/systemd/system/mlocate-updatedb.service;
> static; vendor preset: disable Active: acti
)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
> 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
> ===
>
>
>> Sent: Monday, September 19, 2016 at 10:30 PM
>&g
On 19 September 2016 at 22:38, Patrick Dupre wrote:
> I did:
> systemctl enable mlocate-updatedb.service
> (no error)
> but it still does not seem to be enabled:
> ● mlocate-updatedb.service - Update a database for mlocate
>Loaded: loaded (/usr/lib/systemd/system/mlocate-updatedb.service; stat
| | 59140 Dunkerque, France
===
> Sent: Monday, September 19, 2016 at 10:30 PM
> From: "Andy Blanchard"
> To: "Community support for Fedora users"
> Subject: Re: anacron/cron
>
> It *should*
ue, France
===
> Sent: Monday, September 19, 2016 at 10:29 PM
> From: stan
> To: users@lists.fedoraproject.org
> Subject: Re: anacron/cron
>
> On Mon, 19 Sep 2016 22:04:21 +0200
> "Patrick Dupre" wrote:
>
> > The point is
On Mon, Sep 19, 2016 at 04:28:15PM -0400, Jon LaBadie wrote:
> On Mon, Sep 19, 2016 at 10:04:21PM +0200, Patrick Dupre wrote:
> > The point is that I am not sure that mlocate (or updatedb) runs properly
> > because locate does not find my new files !
> >
> > How can I be sure that mlocate runs pro
==
>
>
>> Sent: Monday, September 19, 2016 at 10:11 PM
>> From: "Joe Zeff"
>> To: "Community support for Fedora users"
>> Subject: Re: anacron/cron
>>
>> On 09/19/2016 01:0
On Mon, Sep 19, 2016 at 03:15:58PM -0400, Tom Horsley wrote:
> On Mon, 19 Sep 2016 20:47:20 +0200
> Patrick Dupre wrote:
>
> > Sorry, but I do not have
> > /etc/cron.daily/mlocate.cron
>
> This is all part of the systemd fungus experience as it
> attempts to engulph all of linux.
>
> An rpm -q
On Mon, 19 Sep 2016 22:04:21 +0200
"Patrick Dupre" wrote:
> The point is that I am not sure that mlocate (or updatedb) runs
> properly because locate does not find my new files !
>
> How can I be sure that mlocate runs properly ?
$ systemctl status mlocate-updatedb.service
● mlocate-updatedb.se
ferent
user, or under a permission protected directory, mlocate
will not show them to you.
Jon
>
>
> > Sent: Monday, September 19, 2016 at 9:15 PM
> > From: "Tom Horsley"
> > To: "Patrick Dupre"
> > Cc: users@lists.fedoraproject.org
> &g
ue, France
===
> Sent: Monday, September 19, 2016 at 10:11 PM
> From: "Joe Zeff"
> To: "Community support for Fedora users"
> Subject: Re: anacron/cron
>
> On 09/19/2016 01:04 PM, Patrick Dupre wrote:
> > How can I be sure that ml
On 09/19/2016 01:04 PM, Patrick Dupre wrote:
How can I be sure that mlocate runs properly ?
If all else fails, run this as root:
ls -l /var/lib/mlocate/mlocate.db
and see when it was last updated.
___
users mailing list -- users@lists.fedoraproject.
ue, France
===
> Sent: Monday, September 19, 2016 at 9:15 PM
> From: "Tom Horsley"
> To: "Patrick Dupre"
> Cc: users@lists.fedoraproject.org
> Subject: Re: anacron/cron
>
> On Mon, 19 Sep 2016 20:47:20 +0200
>
On Mon, 19 Sep 2016 20:47:20 +0200
Patrick Dupre wrote:
> Sorry, but I do not have
> /etc/cron.daily/mlocate.cron
This is all part of the systemd fungus experience as it
attempts to engulph all of linux.
An rpm -q --list mlocate shows these files on my fedora 24
system:
/usr/lib/systemd/system
ue, France
===
> Sent: Monday, September 19, 2016 at 8:37 PM
> From: "Jon LaBadie"
> To: users@lists.fedoraproject.org
> Subject: Re: anacron/cron
>
> On Mon, Sep 19, 2016 at 11:42:42AM +0200, Patrick Dupre w
On Mon, Sep 19, 2016 at 11:42:42AM +0200, Patrick Dupre wrote:
> Hello,
>
...
>
> 3) systemctl | grep -i locate
> provides not answer.
> How can I check that mlocate run properly ?
> There is not service locate or mlocate
locate does not run as a service.
locate's database is updated daily via
8 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===
>
> On 09/19/2016 05:42 AM, Patrick Dupre wrote:
> > Hello,
> >
> > 1) In fc22, ana
On 09/19/2016 05:42 AM, Patrick Dupre wrote:
> Hello,
>
> 1) In fc22, anacron (and crond) sent mail to root every time that it
> was running. How can I recover this function with fc24 ?
>
> 2) Now, anacron and cron work. However, I have
> in /etc/crontab
> 22 23 *
Hello,
Thank for the suggestion.
But, are you sure? I would like to keep running anacron on a machine which
does not run permanently !
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire de Physico-Chimie de
Install cronie-noanacron then remove cronie-anacron.
Anacron should not be setup for servers, but is good for a laptop.
On Mon, 2016-09-19 at 11:42 +0200, Patrick Dupre wrote:
> Hello,
>
> 1) In fc22, anacron (and crond) sent mail to root every time that it
> was running. How can I
Hello,
1) In fc22, anacron (and crond) sent mail to root every time that it
was running. How can I recover this function with fc24 ?
2) Now, anacron and cron work. However, I have
in /etc/crontab
22 23 * * * root run-parts /etc/cron.daily
06 13 * * 6 root run-parts /etc/cron.weekly
and in /ect
Have you considered installing something like IMAP on that machine to make
mail more convenient to read?
Boris.
On Sat, Sep 17, 2016 at 12:25 PM, Bob Goodwin
wrote:
>
> I have been using Linux for a long time and have yet to see a cron/anacron
> mail message.
>
> In [root@Box10
I have been using Linux for a long time and have yet to see a
cron/anacron mail message.
In [root@Box10 bobg]# cat /etc/aliases I configured:
# Person who should get root's mail
root:bobg
And after a bit of googling I dnf installed mail. Mail is difficult to
use, has a long li
On 09/17/2016 07:51 AM, Patrick Dupre wrote:
> Hello,
>
> In my mailbox, I receive emails: Anacron job 'cron.weekly' on
> While I do not receive any amail:
> Anacron job 'cron.daily' on
>
> while it should run daily:
> logrotate
> certwatch
&g
Hello,
In my mailbox, I receive emails: Anacron job 'cron.weekly' on
While I do not receive any amail:
Anacron job 'cron.daily' on
while it should run daily:
logrotate
certwatch
It even more strange, on a fc22 machine I had Anacron job 'cron.daily' on
until July
Still working on cron without sendmail. I am learning some as I peel
the onion. The latest error message is:
Jan 19 16:21:23 lx120e.htt-consult.com run-parts[22838]:
(/etc/cron.daily) finished prelink
Jan 19 16:21:23 lx120e.htt-consult.com anacron[10446]: Job `cron.daily'
termi
On 01/02/2014 08:13 AM, Tom Horsley wrote:
not at some random inconvenient time anacron
picks using the artificial intelligence algorithm it apparently
has to maximize inconvenience :-).
It sounds like anacron is using the same form of AI that a first-person
shooter I like (Joint Operations
On Thu, 2 Jan 2014 10:25:33 -0500 (EST)
Robert P. J. Day wrote:
> normally, i'd interpret that to mean that i can remove that package
> independently of anything else.
I gave up trying to make anacron go away in any sensible fashion.
I just use a "big hammer" to clobber a
On Thu, 2 Jan 2014, Bruno Wolff III wrote:
> On Thu, Jan 02, 2014 at 10:25:33 -0500,
> "Robert P. J. Day" wrote:
> >
> > predictably, cronie-anacron requires cronie, that part's easy.
> >however, if i check to see what "requires" cronie-anacr
On Thu, Jan 02, 2014 at 10:25:33 -0500,
"Robert P. J. Day" wrote:
predictably, cronie-anacron requires cronie, that part's easy.
however, if i check to see what "requires" cronie-anacron on my fedora
20 system, i see:
# rpm -q --whatrequires cronie-anacron
n
slowly getting back to speed on my fedora stuff and i'm a bit
puzzled about the dependency relationship between the packages cronie
and cronie-anacron.
predictably, cronie-anacron requires cronie, that part's easy.
however, if i check to see what "requires" cronie-ana
On 11/18/2010 11:34 AM, Steven Stern wrote:
> On 11/18/2010 10:20 AM, Robert Moskowitz wrote:
>
>> On this F12 server, my /etc/anacrontab is rather simple:
>>
>> SHELL=/bin/sh
>> PATH=/sbin:/bin:/usr/sbin:/usr/bin
>> MAILTO=root
>> # the maximal random delay added to the base delay of the jobs
gt; Nov 18 11:01:01 homebase run-parts(/etc/cron.hourly)[11128]: starting
> 0anacron
> Nov 18 11:01:01 homebase anacron[11138]: Anacron started on 2010-11-18
> Nov 18 11:01:01 homebase run-parts(/etc/cron.hourly)[11140]: finished
> 0anacron
> Nov 18 11:01:01 homebase anacron[11138
;t see any line
there for the hourly, but them run. For /var/log/cron:
Nov 18 11:01:01 homebase CROND[11128]: (root) CMD (run-parts
/etc/cron.hourly)
Nov 18 11:01:01 homebase run-parts(/etc/cron.hourly)[11128]: starting
0anacron
Nov 18 11:01:01 homebase anacron[11138]: Anacron started on 2010-11
A new crontabs package was released that fixed this problem.
crontabs-1.11-1.2010git.fc14.noarch
Alan
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.or
After seeing this bug, I checked on my cron jobs and found
they were not working either. After a bit of investigation
I found the crontabs problem:
https://bugzilla.redhat.com/show_bug.cgi?id=653132
Work around: Find any crontab that is using run-parts
and make sure you add a trailing / to the d
After seeing this bug, I checked on my cron jobs and found
they were not working either. After a bit of investigation
I found the crontabs problem:
https://bugzilla.redhat.com/show_bug.cgi?id=653132
Work around: Find any crontab that is using run-parts
and make sure you add a trailing / to the di
>/ None of the daily or weekly jobs have run since upgrading to fedora 14.
/>/ Jobs in /etc/cron.d are working (denyhosts,sa-update,lmsensor_charts).
/
I go to a lot of trouble to disable anacron, so I've had to discover
how it is enabled in order to disable it. It starts with
On Sun, 14 Nov 2010 09:34:05 -0500
Alan J. Gagne wrote:
> None of the daily or weekly jobs have run since upgrading to fedora 14.
> Jobs in /etc/cron.d are working (denyhosts,sa-update,lmsensor_charts).
I go to a lot of trouble to disable anacron, so I've had to discover
how it is
On 11/14/2010 08:34 AM, Alan J. Gagne wrote:
>> None of the daily or weekly jobs have run since upgrading to fedora 14.
>> Jobs in /etc/cron.d are working (denyhosts,sa-update,lmsensor_charts).
>>
>> I am waiting to see if the daily/weekly jobs run after manually
> None of the daily or weekly jobs have run since upgrading to fedora 14.
> Jobs in /etc/cron.d are working (denyhosts,sa-update,lmsensor_charts).
>
> I am waiting to see if the daily/weekly jobs run after manually
> executing anacron by
> running /etc/cron.hourly/0anacron
>
None of the daily or weekly jobs have run since upgrading to fedora 14.
Jobs in /etc/cron.d are working (denyhosts,sa-update,lmsensor_charts).
I am waiting to see if the daily/weekly jobs run after manually
executing anacron by
running /etc/cron.hourly/0anacron
[linux0]# uname -r
2.6.35.6-48
On Fri, Aug 06, 2010 at 07:23:54AM -0500, inode0 wrote:
> On Fri, Aug 6, 2010 at 5:07 AM, Alexander Volovics
> wrote:
> > Has anyone had this problem after the latest updates.
> >
> > /etc/cron.daily/0logwatch:
> >
> > Can't exec "sendmail": Permission denied at /usr/sbin/logwatch line
> > 1032,
On Fri, Aug 6, 2010 at 5:07 AM, Alexander Volovics wrote:
> Hello
>
> Has anyone had this problem after the latest updates.
> I still get the report:
>
> /etc/cron.daily/0logwatch:
>
> Can't exec "sendmail": Permission denied at /usr/sbin/logwatch line
> 1032,
> + line 2.
> Can't execute sendmail
On 06/08/10 11:07, Alexander Volovics wrote:
No what selinux-policy do you have?
--
Regards,
Frank Murphy
UTF_8 Encoded
Friend of Fedora
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
G
Hello
Has anyone had this problem after the latest updates.
I still get the report:
/etc/cron.daily/0logwatch:
Can't exec "sendmail": Permission denied at /usr/sbin/logwatch line
1032,
+ line 2.
Can't execute sendmail -t: Permission denied
Alexander
--
users mailing list
users@lists.fedorapro
On 5/17/2010 12:57 PM, Tom Horsley wrote:
> On Mon, 17 May 2010 13:08:00 -0500
> Robert Nichols wrote:
>
>
>> In F12 as distributed, anacron is started once an hour by crond
>>
> How does cron do that? Does it "just know" that it should run
> t
On Mon, 17 May 2010 14:57:48 -0400
Tom Horsley wrote:
> How does cron do that? Does it "just know" that it should run
> the hourly jobs? The /etc/crontab shipped with f12 has nothing
> but comments in it...
OK, I finally found /etc/cron.d/0hourly.
--
users mailing list
users@lists.fedoraproject.
On Mon, 17 May 2010 13:08:00 -0500
Robert Nichols wrote:
> In F12 as distributed, anacron is started once an hour by crond
How does cron do that? Does it "just know" that it should run
the hourly jobs? The /etc/crontab shipped with f12 has nothing
but comments in it...
--
users
On 05/17/2010 08:52 AM, Tom Horsley wrote:
> On Mon, 17 May 2010 15:28:51 +0200
> Frank Elsner wrote:
>
>> Is from FC6 but should be same on F12:
>
> Perhaps it should be the same, but in fact it isn't
> even remotely the same. All the anacron and cron stuff
> has b
On 05/17/2010 02:08 PM, Joachim Backes wrote:
> Hi, can somebody tell me when during boot anacron is started, and where
> the startscript is located (F12)?
>
> All comments are welcome.
>
> Kind regards
>
> Joachim Backes
>
> http://www.rhrk.uni-kl.de/~backes
>
On Mon, 17 May 2010 15:28:51 +0200
Frank Elsner wrote:
> Is from FC6 but should be same on F12:
Perhaps it should be the same, but in fact it isn't
even remotely the same. All the anacron and cron stuff
has been completely rejiggered in f12.
I've been able to completely disable
On Mon, 17 May 2010 15:08:54 +0200 Joachim Backes wrote:
> Hi, can somebody tell me when during boot anacron is started, and where
> the startscript is located (F12)?
>
> All comments are welcome.
Is from FC6 but should be same on F12:
/etc/anacrontab
/etc/cron.daily/0anacron
/etc/
Hi, can somebody tell me when during boot anacron is started, and where
the startscript is located (F12)?
All comments are welcome.
Kind regards
Joachim Backes
http://www.rhrk.uni-kl.de/~backes
smime.p7s
Description: S/MIME Cryptographic Signature
--
users mailing list
users
90 matches
Mail list logo
