On 2022-11-21 07:21:12 +0800, Paul Wise wrote:
> To see if a system is affected you can use these commands:
>
>zgrep -i anacron.*2.3-33 /var/log/apt/history.log*
>systemctl status anacron.service anacron.timer
In the first command, the quotes for the grep regexp are missing.
Hi folks,
If you run Debian testing/unstable and ever installed anacron 2.3-33 on
a systemd based system, then anacron will no longer be enabled and the
daily/weekly/monthly cron jobs will not be run until it is.
Since not all cron jobs have migrated to systemd timers, Debian
testing/unstable
On Tue, 4 Oct 2022 11:25:22 -0400
wrote:
> As I mentioned, the email which should
> have been generated did finally arrive, 3 hours later.
Actually, no, you didn't mention it in your original post.
--
Does anybody read signatures any more?
https://charlescurley.com
On Tue, 2022-10-04 at 11:25 -0400, pa...@quillandmouse.com wrote:
> Yes, Exim4, properly configured. As I mentioned, the email which should
> have been generated did finally arrive, 3 hours later. Go figure.
Looking at the email headers would help you figure out where on the
delivery route the
On Tue 04 Oct 2022 at 11:25:22 (-0400), pa...@quillandmouse.com wrote:
> On Tue, 4 Oct 2022 08:21:20 -0600 Charles Curley wrote:
> > On Tue, 4 Oct 2022 09:11:59 -0400 wrote:
> >
> > > Can anyone give me a clue why the output of the script
> > > would fail to generate an email for me?
> >
> > Do
. I checked the contents of /var/mail, and
> > there's no output. FWIW, when run manually, it generates the
> > aforementioned output.
> >
> > I haven't tampered with anacron other than to add the script to the
> > directory above. Can anyone give me a clue why the output of
On Tue, 4 Oct 2022 08:21:20 -0600
Charles Curley wrote:
> On Tue, 4 Oct 2022 09:11:59 -0400
> wrote:
>
> > Can anyone give me a clue why the output of the script
> > would fail to generate an email for me?
>
> Do you have a mail transport agent (MTA) such as postfix or exim
> installed?
>
ementioned output.
>
> I haven't tampered with anacron other than to add the script to the
> directory above. Can anyone give me a clue why the output of the
> script would fail to generate an email for me?
Have you installed mail on the pi? It's not there by default. You may
find messag
On Tue, 4 Oct 2022 09:11:59 -0400
wrote:
> Can anyone give me a clue why the output of the script
> would fail to generate an email for me?
Do you have a mail transport agent (MTA) such as postfix or exim
installed?
--
Does anybody read signatures any more?
https://charlescurley.com
a timestamp file at the end of its backup, and that file
indicates it ran on schedule. However, there is no email containing its
output. I checked the contents of /var/mail, and there's no output.
FWIW, when run manually, it generates the aforementioned output.
I haven't tampered with anacron other
On Wed, 6 Jul 2022 12:07:59 -0400
Timothy M Butterworth wrote:
> On Tue, Jul 5, 2022 at 2:15 PM Chris Mitchell
> wrote:
>
> > I have a unit file named email-notify@.service with contents:
> > [Unit]
> > Description=%i email notification
> >
> > [Service]
> > Type=oneshot
> >
>
On Mon, 4 Jul 2022 23:39:40 +0300
Roland Mueller wrote:
> > On 7/4/22 10:41, Michael wrote:
> >
> > afaik systemd timer lack the possibility to send the output (if any)
> > by email to a designated user, but instead logs the output to its
> > journal.
>
> yes, you are right. If receiving by
Hello,
On 7/4/22 10:41, Michael wrote:
hey,
afaik systemd timer lack the possibility to send the output (if any) by
email to a designated user, but instead logs the output to its journal.
so, if you want/need that functionality, either use a wrapper script, or
define a service with an
hey,
afaik systemd timer lack the possibility to send the output (if any) by
email to a designated user, but instead logs the output to its journal.
so, if you want/need that functionality, either use a wrapper script, or
define a service with an 'ExecStart=' directive looking something
Hello,
ti 28. kesäk. 2022 klo 10.24 Harald Dunkel (harald.dun...@aixigo.com)
kirjoitti:
>
> Hi folks,
>
> I do not like my cron jobs in /etc/cron.daily being ignored or
> delayed for some obfuscated reasons, so I wonder what is the
> recommended alternative to anacron wi
Just use cron.
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
Hi folks,
I do not like my cron jobs in /etc/cron.daily being ignored or
delayed for some obfuscated reasons, so I wonder what is the
recommended alternative to anacron with propper logging by
default? Will systemd take care?
Regards
Harri
Hi,
I installed anacron on my Debian 10 and I just want to be sure to understand
how it works on Debian (I've read there are some distro-dependent
configurations, including Debian) before I have some bad surprises ;)
Let's say I have a specific job "toto" inside /etc/cron.daily. T
On 12/5/18, Kamil Jońca wrote:
> Cindy-Sue Causey writes:
>
>> On 12/5/18, Kamil Jońca wrote:
>>> Michael Biebl writes:
>>>
>>>>
>>>> My general remark that anacron is typically not needed anymore, still
>>>> stands though (
Cindy-Sue Causey writes:
> On 12/5/18, Kamil Jońca wrote:
>> Michael Biebl writes:
>>
>>>
>>> My general remark that anacron is typically not needed anymore, still
>>> stands though (even if it doesn't apply for your specific use case).
>>
>
On 12/5/18, Kamil Jońca wrote:
> Michael Biebl writes:
>
>>
>> My general remark that anacron is typically not needed anymore, still
>> stands though (even if it doesn't apply for your specific use case).
>
> What is other tool to make USER automated, cyclic ta
Michael Biebl writes:
>
> My general remark that anacron is typically not needed anymore, still
> stands though (even if it doesn't apply for your specific use case).
What is other tool to make USER automated, cyclic tasks?
KJ
--
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
W
Am 05.12.18 um 11:35 schrieb Kamil Jońca:
> So I cannot drop (ana)cron :) EOT
With your specific set of requirements, you are most likely best served
by cron (and anacron if your system is not continuously running).
I still don't understand why you need to start your backup task as u
Michael Biebl writes:
> Am 05.12.18 um 11:04 schrieb Kamil Jońca:
>
>> But 'enable-linger' starts my ALL services, which is not what I want.
>> I want to start only timers.
>
> Since you can only have one systemd --user instance, this is not possible.
> You can't have a systemd --user instance
Am 05.12.18 um 11:04 schrieb Kamil Jońca:
> But 'enable-linger' starts my ALL services, which is not what I want.
> I want to start only timers.
Since you can only have one systemd --user instance, this is not possible.
You can't have a systemd --user instance which is started during boot
with
Michael Biebl writes:
[...]
>
>> 2. start timers irrespective of graphical login.
>
> If you want them to be started during boot, use enable-linger
But 'enable-linger' starts my ALL services, which is not what I want.
I want to start only timers.
KJ
--
http://wolnelektury.pl/wesprzyj/teraz/
Am 05.12.18 um 10:49 schrieb Michael Biebl:
> Am 05.12.18 um 10:47 schrieb Kamil Jońca:
>> How can I:
>> 1. start services only with graphical login and
>
> You can't. At least not yet. Use ~/.config/autostart
Some work has already been done to support graphical-session.target
Am 05.12.18 um 10:47 schrieb Kamil Jońca:
> Michael Biebl writes:
>
>> Am 05.12.18 um 10:04 schrieb Kamil Jońca:
>>> Michael Biebl writes:
>>
> which in turn, can break ALL your "user" units)
I'd be interested to know, what exactly you have in mind here. I'm not
aware of
Michael Biebl writes:
> Am 05.12.18 um 10:04 schrieb Kamil Jońca:
>> Michael Biebl writes:
>
which in turn, can break ALL your "user" units)
>>>
>>> I'd be interested to know, what exactly you have in mind here. I'm not
>>> aware of such a breakage.
>>
>> For example: I have (--user)
>>
Am 05.12.18 um 10:04 schrieb Kamil Jońca:
> Michael Biebl writes:
>>> which in turn, can break ALL your "user" units)
>>
>> I'd be interested to know, what exactly you have in mind here. I'm not
>> aware of such a breakage.
>
> For example: I have (--user)
> kj-keepassx.service - my own
ser crontab.
To clarify things:
1. In original post I described system task which CAN (and sooner or
later will) be migrated to systemd timers.
But then You said that:
2. anacron can be dropped - which in general is not true, because
systemd cannot provided proper functionality for user units.
&g
Am 05.12.18 um 08:54 schrieb Kamil Jońca:
> "User" task aren't started until user logs in. (You should play with
> enable-linger,
I haven't read the full discussion, so I missed the part that you are
apparently using a user crontab.
Just curious: Why are you starting the backup task via a user
Michael Biebl writes:
> Am 05.12.18 um 07:41 schrieb Michael Biebl:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864213#25
>> If you drop /lib/udev/rules.d/60-anacron.rules my bet is that the
>> problem is gone.
>
> Btw, I'd go as far and say that you can saf
Am 05.12.18 um 07:41 schrieb Michael Biebl:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864213#25
> If you drop /lib/udev/rules.d/60-anacron.rules my bet is that the
> problem is gone.
Btw, I'd go as far and say that you can safely drop anacron these days.
A lot of Debian packa
Michael Biebl writes:
[...]
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864213#25
> If you drop /lib/udev/rules.d/60-anacron.rules my bet is that the
> problem is gone.
kjonca@alfa:~%ls /lib/udev/rules.d/60-anacron.rules
ls: cannot access '/lib/udev/rules.d/60-anacron.rules': No such
> On Mon, 03 Dec 2018, Kamil Jońca wrote:
>> >> Dec 03 00:23:54 alfa systemd[1]: anacron.service: State 'stop-sigterm'
>> >> timed out. Killing.
>> > See, someone or some script told systemd to stop anacron (or maybe to
>> > stop-and-start/restart
d that way?)
I am no expert of systemd. Heck Im not even a noob!
Just saying that timers seems to be the systemd way in place of cron/anacron
https://unix.stackexchange.com/questions/278564/cron-vs-systemd-timers
>
> Ekhem. My personal cron entries are called regardles I am logged in or
On Mon, 03 Dec 2018, Kamil Jońca wrote:
> >> Dec 03 00:23:54 alfa systemd[1]: anacron.service: State 'stop-sigterm'
> >> timed out. Killing.
> > See, someone or some script told systemd to stop anacron (or maybe to
> > stop-and-start/restart it). THIS is causing th
>> 1. as "everybody" knows, in case of anacron presence, system cron jobs
>> are delegated to anacron.
>> 2. recently in Debian we have anacron.timer which also runs "cron.daily"
>>entry.
>> 3. there is a timeout in systemd services which ca
On Monday, December 3, 2018 at 1:30:07 PM UTC+5:30, Kamil Jońca wrote:
> I have in my /etc/cron.daily some local scripts.
> Some of them can be occassionally time-consuming.
> Recently I found that some of them did not end.
> And what I found:
> 1. as "everybody" knows, in
Henrique de Moraes Holschuh writes:
> On Mon, 03 Dec 2018, Kamil Jońca wrote:
>> 1. as "everybody" knows, in case of anacron presence, system cron jobs
>> are delegated to anacron.
>> 2. recently in Debian we have anacron.timer which also runs "cron.daily&qu
Kamil Jońca wrote:
> Here is some journal excerpt:
> Dec 03 00:23:54 alfa systemd[1]: anacron.service: State 'stop-sigterm'
> timed out. Killing. Dec 03 00:23:54 alfa systemd[1]: anacron.service:
> Killing process 8919 (anacron) with signal SIGKILL. Dec 03 00:23:54 alfa
On Mon, 03 Dec 2018, Kamil Jońca wrote:
> 1. as "everybody" knows, in case of anacron presence, system cron jobs
> are delegated to anacron.
> 2. recently in Debian we have anacron.timer which also runs "cron.daily"
>entry.
> 3. there is a timeout in syst
I have in my /etc/cron.daily some local scripts.
Some of them can be occassionally time-consuming.
Recently I found that some of them did not end.
And what I found:
1. as "everybody" knows, in case of anacron presence, system cron jobs
are delegated to anacron.
2. recently in Debi
> See the thread started by John Cunningham on this very mailing list on
> this topic 6 days before you did.
I had read this before, but the problem reported there seemed to be quite
different from mine.
As I said, anacron refused to do anything when started manually. I tried
to star
Michael Lange:
[...] I discovered that the syslog had become rather huge, so
apparently logrotate had not been performed for months.
See the thread started by John Cunningham on this very mailing list on
this topic 6 days before you did.
Hi,
on my laptop (with Stretch) anacron for some reason refuses to work, which
I only noticed initially when I discovered that the syslog had become
rather huge, so apparently logrotate had not been performed for months.
cron itself is working, which I can tell by a custom script
in /etc
Hello,
By default, mdadm is set to run /usr/etc/mdadm/checkarray monthly to check
the arrays for consistency: see /etc/cron.d/mdadm . This is all well and
good, except if the machine is off at that time.
Is getting anacron to pick this up on a monthly as simple as putting the
relevant /etc
On Friday 05 December 2014 23:44:27 Sven Joachim wrote:
On 2014-12-05 23:24 +0100, Rainer Dorsch wrote:
I have one machine here on which cron.daily is not run reliably with
anacron.
I see in
rd@blackbox:~/Managed/LinuxInst$ grep cron.daily /var/log/syslog
Dec 1 22:55:11 blackbox
Hello,
I have one machine here on which cron.daily is not run reliably with anacron.
I see in
rd@blackbox:~/Managed/LinuxInst$ grep cron.daily /var/log/syslog
Dec 1 22:55:11 blackbox anacron[14161]: Job `cron.daily' terminated (mailing
output)
rd@blackbox:~/Managed/LinuxInst$
i.e. it run
On 2014-12-05 23:24 +0100, Rainer Dorsch wrote:
I have one machine here on which cron.daily is not run reliably with anacron.
I see in
rd@blackbox:~/Managed/LinuxInst$ grep cron.daily /var/log/syslog
Dec 1 22:55:11 blackbox anacron[14161]: Job `cron.daily' terminated (mailing
output
Bob Proulx b...@proulx.com writes:
The particular part I was pedantically talking about was your comment
that said checks that it is executable, yes, all good, and then you
go on to say *and* sees to it that this user has permission. It was
that last part, the second part of the _and_ that I
Harry Putnam wrote:
Bob Proulx writes:
commenting upon. Because while true for non-root for root if it is
root there isn't any user test. For the root user it is purely a
Alright... at last. I've been laying for a chance to pedantic right
back at you...
:-)
check to see if there is
Bob Proulx b...@proulx.com writes:
Harry Putnam wrote:
I'm still not getting the whole picture of what is supposed to happen
on a machine with both anacron and cron installed.
And you might be tired of having me respond about it. :-)
Not on your life! I have a certain fondness
Harry Putnam wrote:
Bob Proulx writes:
Harry Putnam wrote:
I'm still not getting the whole picture of what is supposed to happen
on a machine with both anacron and cron installed.
And you might be tired of having me respond about it. :-)
Not on your life! I have a certain fondness
I'm still not getting the whole picture of what is supposed to happen
on a machine with both anacron and cron installed.
I understand the reasoning for machines that are not up all the time,
where anacron picks up the slack for cron jobs that came up with
the machine down.
I get that.
But in my
Harry Putnam wrote:
I'm still not getting the whole picture of what is supposed to happen
on a machine with both anacron and cron installed.
And you might be tired of having me respond about it. :-)
I have lines like the one below in /etc/crontab
[...] test -x /usr/sbin/anacron || ( cd
Hi
Can someone please help me understand the difference between cron anacron
fcron and are there any linux schedulers available in Linux ?
Regards
Kaushal
On 07/01/12 13:52, Kaushal Shriyan wrote:
Hi
Can someone please help me understand the difference between�cron
anacron fcron
cron - best on constantly running machines
anacron - for machines that aren't always running, it'll try and trigger
events when it is
fcron - has features of both
Hola,
Quiero hacerles una pregunta a los versados y escuchar sus comantarios.
anacron y cron, son la misma cosa o dos cosas diferentes que realizan
tareas similares?
--
Saludos,
Luis Esteban
Linuxero por cuenta propia
Cuba
If Debian GNU/Linux can do it, you can do it too...
--
Este
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luis escribió:
Hola,
Quiero hacerles una pregunta a los versados y escuchar sus comantarios.
anacron y cron, son la misma cosa o dos cosas diferentes que realizan
tareas similares?
Buenas
De la wiki:
A diferencia de cron, anacron
El día 14 de julio de 2011 17:21, Luis este...@princesa.pri.sld.cu escribió:
Hola,
Quiero hacerles una pregunta a los versados y escuchar sus comantarios.
anacron y cron, son la misma cosa o dos cosas diferentes que realizan tareas
similares?
--
Saludos,
Son cosas distintas.
Si lo
El jueves, 14 de julio de 2011 a las 17:26:39 +0200 horas,
jmramirez (mas_ke_na) escribió:
Es una herramienta complementaria, no sustituye al cron.
Anacron tiene sentido cuando no hay garantías de que el equipo esté
funcionando cuando cron tenga que lanzar una tarea. Típicamente un PC
de
El jue, 14-07-2011 a las 11:21 -0400, Luis escribió:
anacron y cron, son la misma cosa o dos cosas diferentes que realizan
tareas similares?
$ apt-cache show anacron
Description-es: programa parecido a cron que no va por tiempo
Anacron (como «anacrónico») es un programador de tareas
En Thu, 14 Jul 2011 11:40:33 -0400, Manolo Díaz du...@pleione.es
escribió:
El jueves, 14 de julio de 2011 a las 17:26:39 +0200 horas,
jmramirez (mas_ke_na) escribió:
Es una herramienta complementaria, no sustituye al cron.
Anacron tiene sentido cuando no hay garantías de que el equipo
En Thu, 14 Jul 2011 11:42:52 -0400, Julio jul...@escomposlinux.org
escribió:
El jue, 14-07-2011 a las 11:21 -0400, Luis escribió:
anacron y cron, son la misma cosa o dos cosas diferentes que realizan
tareas similares?
$ apt-cache show anacron
Description-es: programa parecido a cron que
Hola,
Por lo que tengo entendido, anacron esta diseñado para maquinas que no
están 24x7 como los servers, es decir maquinas de entorno de usuario, la
gran diferencia radica, en lo siguiente.
Cron:
Cuando tienes especificado una tarea supongamos a las 11pm, y el host
esta apagado, la tarea
En Thu, 14 Jul 2011 11:29:52 -0400, Gerardo Villafranca
gerardovillafra...@gmail.com escribió:
Hola,
Por lo que tengo entendido, anacron esta diseñado para maquinas que no
están 24x7 como los servers, es decir maquinas de entorno de usuario, la
gran diferencia radica, en lo siguiente.
Cron
Am 15.09.2010 10:51, schrieb Camaleón:
Anacron or cron? It seems they are two different packages :-?
Yes, they are. As far as I understand it, anacron makes sure that cron
jobs are run even if the machine is not up 24/7.
Those bug reports are for cron and should be already fixed.
I
and some lines from the mail I received,
somewhat edited to protect my privacy and save bandwidth:
--- snip ---
Betreff: Anacron job 'cron.daily' on server Von: Anacron
r...@server.domain.tld Datum: Tue, 14 Sep 2010 07:44:48 +0200 An:
r...@server.domain.tld
(...)
Thanks
with local (Exim 4.69)
(envelope-from r...@server.domain.tld)
id 1OvOK0-00051N-GV
for r...@server.domain.tld; Tue, 14 Sep 2010 07:44:48 +0200
From: Anacron r...@server.domain.tld
To: r...@server.domain.tld
Subject: Anacron job 'cron.daily' on server
Message-Id: e1ovok0-00051n
-mail (provided that there is no
Content-Type:). So if anacron is using the same routine to send e-
mails than cron, it looks like a bug/error here to me.
Anyway, you can try the bypass suggested by the manual (define
CONTENT_TYPE and CONTENT_TRANSFER_ENCODING variables in the offending
anacron
, to the correct values of the mail headers of those names
***
Which does not comply with your e-mail (provided that there is no
Content-Type:). So if anacron is using the same routine to send e-
mails than cron, it looks like a bug/error here to me.
Anyway, you can try the bypass
On 2010-09-16 15:11 +0200, Malte Forkel wrote:
I think I have to convince anacron to use Content-* headers. But I'm not
sure I can do that with the environment variables that cron uses.
Indeed you can't, you would have to write the code to insert the
Content-* headers in the first place. Look
On Thu, 16 Sep 2010 15:11:51 +0200, Malte Forkel wrote:
Am 16.09.2010 13:00, schrieb Camaleón:
As per man 5 crontab:
(...)
Which does not comply with your e-mail (provided that there is no
Content-Type:). So if anacron is using the same routine to send e-
mails than cron, it looks like
Am 16.09.2010 15:28, schrieb Sven Joachim:
Indeed you can't, you would have to write the code to insert the
Content-* headers in the first place. Look at the launch_job function
in runjob.c in the anacron source.
That looks just like the right spot. Thanks, Sven!
I wrote to anacron's
On Tue, 14 Sep 2010 17:54:17 +0200, Malte Forkel wrote:
I'm using anacron for some tasks on a machine running Lenny. Error
output from those jobs send by email looks strange in Thunderbird.
Anacron or cron? It seems they are two different packages :-?
Mails send by cron supposedly respect
On Wed, 15 Sep 2010 08:51:01 + (UTC)
Camaleón noela...@gmail.com wrote:
Hello Camaleón,
Anacron or cron? It seems they are two different packages :-?
They are; Anacron is recommended for machines that aren't up 24/7 so
missed cron jobs (many are run overnight by default) get run as soon
Hi,
I'm using anacron for some tasks on a machine running Lenny. Error
output from those jobs send by email looks strange in Thunderbird.
Mails send by cron supposedly respect the locale and include a content
type header, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405335
(cron does
I just installed Sid on this BlueWhite PowerMac G3.
This showed up in root's email-box.
Anybody know what it's all about?
Thanks!
Rick
On May 16, 2010, at 7:59 AM, Anacron wrote:
/etc/cron.weekly/apt-xapian-index:
Traceback (most recent call last):
File /usr/sbin/update-apt-xapian-index
On 2010-05-17 20:07 +0200, Rick Thomas wrote:
On May 16, 2010, at 7:59 AM, Anacron wrote:
/etc/cron.weekly/apt-xapian-index:
Traceback (most recent call last):
File /usr/sbin/update-apt-xapian-index, line 71, in module
warnings.filterwarnings(ignore,)
NameError: name 'warnings
With anacron installed /etc/crontab actually does not start a daily task in
/etc/cron.daily; the line
25 6* * * roottest -x /usr/sbin/anacron || ( cd / run-parts
--report
/etc/cron.daily )
(without line break) just tests if anacron is executable.
Actually, anacron itself is startet
untrained eye, to be anacron restarting cron jobs every
morning --- why? and how does it arrive at 7:35? The README.Debian
indicates the anacron is absolutely transparent. Is there something
else that restarts anacron?
The computer is running plain vanilla desktop Lenny, installed a couple
[skipping a lot of lines ...]
Paul I leave my computer on overnight just so I can have this job
Paul done, but there are indications in the log that seem, to my
Paul untrained eye, to be anacron restarting cron jobs every morning
Paul --- why? And how does it arrive at 7:35
On 08.04.09 10:23, Daniel Dalton wrote:
Are the following lines in /etc/anacrontab ok? Anyway to verify they
will work or do I just have to wait?
1 20 rsnapshot_day /usr/bin/rsnapshot daily
7 35 rsnapshot_weekly /usr/bin/rsnapshot weekly
@monthly
Hi,
Are the following lines in /etc/anacrontab ok? Anyway to verify they
will work or do I just have to wait?
Here are the lines:
1 20 rsnapshot_day /usr/bin/rsnapshot daily
7 35 rsnapshot_weekly /usr/bin/rsnapshot weekly
@monthly50
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
More information, sorry I didn't think to include this in the prior
message.
Any ideas?
=
$ dpkg -l | grep awk
ii gawk1:3.1.5.dfsg-4.1 GNU awk, a pattern scanning and
processing l
ii mawk1.3.3-11.1 a pattern scanning and text
-
- -- Forwarded Message --
Subject: Anacron job 'cron.daily'
Date: Friday 27 March 2009
From: Anacron r...@d
To: r...@d
/etc/cron.daily/htdig:
/etc/cron.daily/htdig: line 18: awk: command not found
/etc/cron.daily/standard:
/etc/cron.daily/standard: line 66: awk: command not found
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok, I've found the problem.
Although ls -al /usr/bin/awk comes back with nothing, if I cd
to /usr/bin and do a dir, I get the following:
==
- -rwxr-xr-x 1 root root 64136 2008-11-16 09:18 avisync
l? ? ? ?
Curt Howland wrote:
==
- -rwxr-xr-x 1 root root 64136 2008-11-16 09:18 avisync
l? ? ? ? ?? awk
- -rwxr-xr-x 1 root root 39828 2008-04-16 18:37 barcode
==
There's some filesystem corruption. Are you familiar with fsck?
On Fri,27.Mar.09, 08:27:10, Curt Howland wrote:
This is the second day I've gotten this error, on up-to-date Lenny.
I'm going to go look for what package awk should be in, but I cannot
imagine why it would be missing. Aren't grep awk and sed the
basic building blocks of all UNIX?
The
On Fri,27.Mar.09, 08:50:35, Curt Howland wrote:
More information, sorry I didn't think to include this in the prior
message.
Any ideas?
=
$ dpkg -l | grep awk
ii gawk1:3.1.5.dfsg-4.1 GNU awk, a pattern scanning and
processing l
ii mawk1.3.3-11.1 a pattern scanning
Hi All
I'm confused about running anacron and cron at the same time. I was
under the impression that it was either/or, but I see on a server
running here that it has both cron and anacron. IIUC, anacron keeps
track of jobs it runs, and marks down the completion time so it knows
when it needs
On Tue, Jul 8, 2008 at 1:15 PM, Brian McKee [EMAIL PROTECTED] wrote:
How does anacron know that
cron already ran that job and it doesn't need to?
Found my answer - there's a script called 0anacron in /etc/cron.daily
that runs 'anacron -u cron.daily' which updates anacron's time stamps
without
On 2008-07-08 19:15 +0200, Brian McKee wrote:
I'm confused about running anacron and cron at the same time. I was
under the impression that it was either/or, but I see on a server
running here that it has both cron and anacron.
Just look at anacron's dependencies, it recommends cron.
IIUC
When I moved to Etch, I noticed something strange, and
am looking for an explanation. My cron job for doing
daily backups started doing the job at the wrong time.
It turns out that the move to Etch somehow installed
anacron on a system that is supposed to be left on and
it was anacron
On Fri, Apr 13, 2007 at 13:09:43 -0600, Paul E Condon wrote:
When I moved to Etch, I noticed something strange, and
am looking for an explanation. My cron job for doing
daily backups started doing the job at the wrong time.
It turns out that the move to Etch somehow installed
anacron
.
It turns out that the move to Etch somehow installed
anacron on a system that is supposed to be left on and
it was anacron that was actually running the script.
But how? I look at the code in /etc/crontab and in
/etc/cron.daily/0anacron and I think I see that it
is impossible
for doing
daily backups started doing the job at the wrong time.
It turns out that the move to Etch somehow installed
anacron on a system that is supposed to be left on and
it was anacron that was actually running the script.
But how? I look at the code in /etc/crontab
On Fri, Apr 13, 2007 at 08:34:31PM -0600, Paul E Condon wrote:
snip...
computer. All set up as part of a standard install. It works, and
not that I know how, I can make it do its stuff when I want.
^^^ s/not/now/
--
Paul E Condon
[EMAIL PROTECTED]
--
To UNSUBSCRIBE,
1 - 100 of 313 matches
Mail list logo
