Once upon a time, Tim said:
> On Sat, 2024-06-22 at 23:02 +0200, Patrick Dupre via users wrote:
> > Even if I remove the x right ?
>
> That kind of thing will always depend on how a script is handled.
They do need to be executable for run-parts to run them. There are a
handful of filenames that
On Sat, 2024-06-22 at 23:02 +0200, Patrick Dupre via users wrote:
> Even if I remove the x right ?
That kind of thing will always depend on how a script is handled.
If it's run directly by a shell, then the shell *may* care about
eXecute bit. Likewise, if its *run* by a handler. But if it's
ess
> Subject: Re: crond
>
> On Jun 22, 2024, at 10:34, Patrick Dupre via users
> wrote:
> >
> > ls -la /etc/cron.weekly/
> >
> > drwxr-xr-x. 2 root root 4096 Jun 22 16:14 .
> > drwxr-xr-x. 248 root root 20480 Jun 22 16:04 ..
> > -rwxr-xr-x.
On Jun 22, 2024, at 10:34, Patrick Dupre via users
wrote:
>
> ls -la /etc/cron.weekly/
>
> drwxr-xr-x. 2 root root 4096 Jun 22 16:14 .
> drwxr-xr-x. 248 root root 20480 Jun 22 16:04 ..
> -rwxr-xr-x. 1 root root 1685 Jun 8 16:17 backup3
> -rwxr-xr-x. 1 root root 3563 Jun 8 16:36 back
Good, it seems that (during the update?), a backup.cron.saved has been created.
I guess that I can just moved to backup.cron_saved
> Sent: Saturday, June 22, 2024 at 4:25 PM
> From: "Doug Herr"
> To: "Fedora Users"
> Cc: "Patrick Dupre"
> Subject: R
On Sat, Jun 22, 2024, at 7:17 AM, Patrick Dupre via users wrote:
> Hello,
>
> I have a backup launched by cron.weekly
> However, since F40, after it has run a first time and ended, another backup
> is started. This messed up the backup.
>
> When starting, the first crond
>
Hello,
I have a backup launched by cron.weekly
However, since F40, after it has run a first time and ended, another backup
is started. This messed up the backup.
When starting, the first crond
sent
(ps -aux | grep -i backup | mail -s Backup root@localhost.localdomain)
root 19672 0.0 0.0
OK Thanks.
It works now
>
> On Fri, 2023-07-28 at 14:10 +0200, Patrick Dupre wrote:
> > I have the same /etc/hosts on 2 machines
> > 127.0.0.1 localhost localhost.localdomain localhost4
> > localhost4.localdomain4
> > ::1 localhost localhost.localdomain localhost6
> > localhost6.locald
On Fri, 2023-07-28 at 14:10 +0200, Patrick Dupre wrote:
> I have the same /etc/hosts on 2 machines
> 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
>
> In one case
> /etc/hostname
> Teu
>
> > Date: Friday, July 28, 2023 12:12:04 +0200
> > From: Patrick Dupre
> >
> > Sorry, I am wrong.
> > crond is OK,
> > but sendmail is wrong.
> >
> > Subject: Unit failed
> > ░░ Defined-By: systemd
> > ░░ Support:
&
> Date: Friday, July 28, 2023 12:12:04 +0200
> From: Patrick Dupre
>
> Sorry, I am wrong.
> crond is OK,
> but sendmail is wrong.
>
> Subject: Unit failed
> ░░ Defined-By: systemd
> ░░ Support:
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░
Sorry, I am wrong.
crond is OK,
but sendmail is wrong.
Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit sendmail.service has entered the 'failed' state with result
'timeout'.
Jul 28 12:08
└─10-timeout-abort.conf
Active: active (running) since Tue 2023-07-25 20:06:32 CEST; 2 days ago
Main PID: 1496 (crond)
Tasks: 1 (limit: 38199)
Memory: 1.4G
CPU: 1h 11min 58.656s
CGroup: /system.slice/crond.service
└─1496 /usr/sbin/crond -n
Jul 28 10
> On Dec 11, 2021, at 13:45, Patrick Dupre wrote:
>
> and here /etc/crontab
> 22 23 * * * root run-parts /etc/cron.daily
> 30 12 * * 6 root run-parts /etc/cron.weekly
Ah. This is why you are getting two jobs. /etc/crontab should not have those
two lines. There should be an /etc/cron.hourly/0a
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 here - Anacron
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 08Jul2020 22:32, Patrick Dupre wrote:
>Running
> systemctl status crond
>
>I get
>crond.service - Command Scheduler
> Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor
> pre>
> Active: active (running) since Wed 2020-07-08 20:44:30 CEST
On Jul 8, 2020, at 16:34, Patrick Dupre wrote:
>
> Why cron.weekly does not show up?
Look in /etc/anacrontab.
--
Jonathan Billings
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproje
Running
systemctl status crond
I get
crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor pre>
Active: active (running) since Wed 2020-07-08 20:44:30 CEST; 1h 42min ago
Main PID: 1415 (crond)
Tasks: 1 (limit: 9
On 04/24/2017 03:22 AM, M. Fioretti wrote:
I DO remember that I created an empty esmtprc, for testing, and
then when restarted crond would complain that:
"Local delivery not possible without a MDA"
Right. If you wanted local delivery, you'd probably install the
"esmtp
On 2017-04-21 08:59, M. Fioretti wrote:
Greetings,
a few minutes ago, I realized that, on a Fedora 25 box I have...
- my /var/log/messages was almost 15 MILLIONS lines long.
- 99% of those lines (~20/second) are like this:
crond: No configuration file found at /home/marco/.esmtprc or
/etc
On 04/21/2017 10:03 AM, Rick Stevens wrote:
That's odd as cron only checks its tables once a minute. It's almost as
if there's a script in a loop with a "sleep 20" or something akin to it
inside the loop or a program doing the same.
I read 20/second as 20 times per second.
It's interesting th
On 04/21/2017 03:15 PM, Cameron Simpson wrote:
2: What uses estmp?
esmtp will provide /usr/sbin/sendmail if it's the only MTA installed, in
which case cronie will use it to deliver job output.
___
users mailing list -- users@lists.fedoraproject.o
On 04/20/2017 11:59 PM, M. Fioretti wrote:
crond: No configuration file found at /home/marco/.esmtprc or
/etc/esmtprc
but the only line in my own crontab is a shell script that runs every
minute. When I run that script manually, from the command line, it
yelds no error or warning.
At
On 04/20/2017 11:59 PM, M. Fioretti wrote:
> Greetings,
>
> a few minutes ago, I realized that, on a Fedora 25 box I have...
>
> - my /var/log/messages was almost 15 MILLIONS lines long.
> - 99% of those lines (~20/second) are like this:
>
> crond: No configuration f
On Fri, 21 Apr 2017 08:59:17 +0200
"M. Fioretti" wrote:
> Greetings,
>
> a few minutes ago, I realized that, on a Fedora 25 box I have...
>
> - my /var/log/messages was almost 15 MILLIONS lines long.
> - 99% of those lines (~20/second) are like this:
>
>
On 21Apr2017 08:59, M. Fioretti wrote:
a few minutes ago, I realized that, on a Fedora 25 box I have...
- my /var/log/messages was almost 15 MILLIONS lines long.
- 99% of those lines (~20/second) are like this:
crond: No configuration file found at /home/marco/.esmtprc or
/etc/esmtprc
but
Greetings,
a few minutes ago, I realized that, on a Fedora 25 box I have...
- my /var/log/messages was almost 15 MILLIONS lines long.
- 99% of those lines (~20/second) are like this:
crond: No configuration file found at /home/marco/.esmtprc or
/etc/esmtprc
but the only line in my own
Den 2016-04-10 kl. 19:27, skrev Jon Ingason:
> I have problem with mail from crond. I have cron job which sends mail to
> root. I get following line in /var/log/maillog:
>
> Apr 8 15:00:03 lea sSMTP[1954]: Invalid response SMTP server
>
> I have google this and have not found
I have problem with mail from crond. I have cron job which sends mail to
root. I get following line in /var/log/maillog:
Apr 8 15:00:03 lea sSMTP[1954]: Invalid response SMTP server
I have google this and have not found any solution that works for me. It
worked very well before Fedora abandoned
Kevin Fenzi wrote:
> If you feel the output is incorrect or could be improved, please file a
> bug on cronie?
>
> https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=15&component=cronie
>
> kevin
Thanks, Kevin, i will do it.
Franta
--
users mailing list
users@lists.fedoraproject.
If you feel the output is incorrect or could be improved, please file a
bug on cronie?
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=15&component=cronie
kevin
signature.asc
Description: PGP signature
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or chan
Larry Brower wrote:
> On 09/12/2011 05:55 PM, Frantisek Hanzlik wrote:
>> CROND in Fedora 14- distros are OK, crond childs are running with
>> this name. But, what shit are F15 crond records (usually directed to
>> "/var/log/cron") aka:
>>
>> Sep 13 00
On 09/12/2011 05:55 PM, Frantisek Hanzlik wrote:
> CROND in Fedora 14- distros are OK, crond childs are running with
> this name. But, what shit are F15 crond records (usually directed to
> "/var/log/cron") aka:
>
> Sep 13 00:30:01 x /USR/SBIN/CROND[11095]: (root) CMD (/
CROND in Fedora 14- distros are OK, crond childs are running with
this name. But, what shit are F15 crond records (usually directed to
"/var/log/cron") aka:
Sep 13 00:30:01 x /USR/SBIN/CROND[11095]: (root) CMD (/usr/local/...
I hope that isn't next step nearer to ass of some c
I am trying to find the program that is causing the crond: System error.
May 10 14:01:01 computer crond[12070]: System error
May 10 14:10:01 computer crond[12147]: System error
May 10 14:20:01 computer crond[12151]: System error
May 10 14:30:01 computer crond[12152]: System error
May 10 14:40:01
42 matches
Mail list logo
