On Tue, Sep 12, 2023 at 00:54 Kushal Kumaran wrote:
> On Mon, Sep 11 2023 at 05:59:37 AM, Tom Browder
> wrote:
> > Anyone using that system? It looks interesting to me.
> >
> I prefer healthchecks.io, mainly because cron job monitoring was all I
> was looking for, and the software is open
On Mon, Sep 11 2023 at 05:59:37 AM, Tom Browder wrote:
> Anyone using that system? It looks interesting to me.
>
I prefer healthchecks.io, mainly because cron job monitoring was all I
was looking for, and the software is open source.
There is a comparison with cronitor at
On Mon, Sep 11, 2023 at 05:08:04PM +, Andrew M.A. Cater wrote:
> On Mon, Sep 11, 2023 at 06:49:00PM +0200, to...@tuxteam.de wrote:
> > On Mon, Sep 11, 2023 at 05:31:45PM +0200, Thomas Schmitt wrote:
> > > Hi,
> > >
> > > to...@tuxteam.de wrote:
> > > > and we're all twins [1] ;-)
> > > > [1]
On Mon, Sep 11, 2023 at 06:49:00PM +0200, to...@tuxteam.de wrote:
> On Mon, Sep 11, 2023 at 05:31:45PM +0200, Thomas Schmitt wrote:
> > Hi,
> >
> > to...@tuxteam.de wrote:
> > > and we're all twins [1] ;-)
> > > [1] https://en.wikipedia.org/wiki/Thomas_(name)
> >
> > But paradoxly less than half
On Mon, Sep 11, 2023 at 05:31:45PM +0200, Thomas Schmitt wrote:
> Hi,
>
> to...@tuxteam.de wrote:
> > and we're all twins [1] ;-)
> > [1] https://en.wikipedia.org/wiki/Thomas_(name)
>
> But paradoxly less than half of all twins bear this very cool name.
Which is a pity, ain't it ;-)
Imagine
Hi,
to...@tuxteam.de wrote:
> and we're all twins [1] ;-)
> [1] https://en.wikipedia.org/wiki/Thomas_(name)
But paradoxly less than half of all twins bear this very cool name.
Have a nice day :)
Thomas
On Mon, Sep 11, 2023 at 07:46:35AM -0500, Tom Browder wrote:
[...]
> > "Apt search monitor" and subsequent filtering with "web" yields half
> > a dozen other interesting hits.
>
>
> Thanks, Tomas, I was not savy enough to think of that!
Glad to help :)
> P.S. We share a good, Biblical name,
On Mon, Sep 11, 2023 at 07:25 wrote:
> On Mon, Sep 11, 2023 at 06:46:43AM -0500, Tom Browder wrote:
> > On Mon, Sep 11, 2023 at 06:22 wrote:
> >
> > > On Mon, Sep 11, 2023 at 05:59:37AM -0500, Tom Browder wrote:
> > > > Anyone using that system? It looks interesting to me.
> > >
> > > Gah. My
On Mon, Sep 11, 2023 at 05:59:37AM -0500, Tom Browder wrote:
> Anyone using that system? It looks interesting to me.
Gah. My eyes hurt now after having looked at the web site.
Besides, it looks a bit like a bait-and-switch SaSS.
No, I wouldn't use it.
Cheers
--
t
signature.asc
Description:
Anyone using that system? It looks interesting to me.
-Tom
On Du, 06 dec 20, 12:23:43, Martin McCormick wrote:
>
> An on-going problem about self-education is that it's
> easy to limit the scope so much that we miss connections.
> Systemd timers doesn't even sound like a replacement for cron but
> think of it as cron on steroids.
It is also a
Andrei POPESCU writes:
> On Jo, 03 dec 20, 07:39:14, Martin McCormick wrote:
> >
> > So, I need to read more general information about the
> > differences between systemd and what we've been using up to
> > recently.
>
> The Wikipedia page and/or https://systemd.io might be a good place to
On Jo, 03 dec 20, 07:39:14, Martin McCormick wrote:
>
> So, I need to read more general information about the
> differences between systemd and what we've been using up to
> recently.
The Wikipedia page and/or https://systemd.io might be a good place to
start.
Kind regards,
Andrei
--
Hi David,
On Fri, Dec 04, 2020 at 01:32:35PM +1100, David wrote:
> On Fri, 4 Dec 2020 at 13:10, Andy Smith wrote:
> > So much text written without clear statement of problem!
>
> I understand why you wrote that, but you might be unaware that
> Martin has previously mentioned on this list that
On Fri, 4 Dec 2020 at 13:10, Andy Smith wrote:
[...]
> I am surprised that just looking up documentation
> on systemd timers doesn't answer that question for you.
[...]
> So much text written without clear statement of problem!
I understand why you wrote that, but you might be unaware that
Hello,
On Thu, Dec 03, 2020 at 07:39:14AM -0600, Martin McCormick wrote:
> I am guilty as charged but haven't yet found the relevant information
> as to how systemd helps solve this issue.
You can put a time zone in a systemd timer. I can't see how it can
be stated any simpler than that.
If you
Martin McCormick writes:
> I record a news broadcast from one of the BBC services
> every week day at 17:45 British time. When Europe and North
> America stop or start shifting daylight in Autumn or Spring,
> there's a really good chance of missing some of the broadcasts if
> one doesn't
> On Wed, Dec 02, 2020 at 01:58:45PM +, James B wrote:
> > This might be wrong, but as far as I understand doesn't systemd
> > now have the ability to manage cron jobs (as well as mount points,
> > home folders and other things)?. Is there anything in this newer
> &g
On Wed, Dec 02, 2020 at 01:17:02PM -0500, Dan Ritter wrote:
> As a name for the utility, I suggest "do-if-time-in" and require
> three parameters:
>
> do-if-time-in timezone time "command"
>
> As an interim fix, though: (and I know Greg's going to fix this)
>
> ---
> #!/bin/bash
> TZ=$1
>
Martin McCormick wrote:
> Greg Wooledge writes:
> > I was vaguely thinking of a similar approach. Set up a job that runs
> > every hour, or across a set of hours that will cover all the possible
> > cases that you care about, in your crontab. Within the job itself,
> > set a TZ variable and
Greg Wooledge writes:
> I was vaguely thinking of a similar approach. Set up a job that runs
> every hour, or across a set of hours that will cover all the possible
> cases that you care about, in your crontab. Within the job itself,
> set a TZ variable and determine the time in that time zone
erstand doesn't systemd
> > now have the ability to manage cron jobs (as well as mount points,
> > home folders and other things)?. Is there anything in this newer
> > functionality that might make such a thing (re the request at the
> > beginning of this thread) possible?
Hello,
On Wed, Dec 02, 2020 at 01:58:45PM +, James B wrote:
> This might be wrong, but as far as I understand doesn't systemd
> now have the ability to manage cron jobs (as well as mount points,
> home folders and other things)?. Is there anything in this newer
> functionality tha
On Wed, Dec 02, 2020 at 08:53:28AM -0500, Dan Ritter wrote:
> It would not be ridiculous to run a wrapper program out of, e.g.
> cron.hourly, which used an explicitly set TZ as a cue to run
> another job.
I was vaguely thinking of a similar approach. Set up a job that runs
every hour, or across
ther country.
>
> As far as I understand cron, one can set the system's
> time zone to only one value which is usually one's local clock
> time and that works very well since system logs and cron jobs all
> agree with what is appropriate for one's location.
>
> I
This might be wrong, but as far as I understand doesn't systemd now have the
ability to manage cron jobs (as well as mount points, home folders and other
things)?. Is there anything in this newer functionality that might make such a
thing (re the request at the beginning of this thread
Greg Wooledge wrote:
> On Wed, Dec 02, 2020 at 07:30:22AM -0600, Martin McCormick wrote:
> > In a recent discussion, someone indicated that there might be a
> > way to set individual parts such as accounts on a unix system so
> > that cron could use another time zone if needed to kickoff jobs
> >
On Wed, Dec 02, 2020 at 07:30:22AM -0600, Martin McCormick wrote:
> In a recent discussion, someone indicated that there might be a
> way to set individual parts such as accounts on a unix system so
> that cron could use another time zone if needed to kickoff jobs
> on that system based on the
the system's
time zone to only one value which is usually one's local clock
time and that works very well since system logs and cron jobs all
agree with what is appropriate for one's location.
I record a news broadcast from one of the BBC services
every week day at 17:45 British time. When
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 (even if it doesn't apply for your specific use case).
>>>
>>> What is
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).
>>
>> What is other tool to make USER automated, cyclic
never had enough brain cells
functioning at the same time to actually pursue finding an excuse to
test drive the concept.
True story is that cron jobs always sounded almost too... "daunting".
Kalarm pulling up in this mix, including via its "apt-cache show"
description, j
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
We totally
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 user
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
Michael Biebl writes:
> 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.
To clarify things:
1. In
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 safely drop anacron these days.
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 packages which
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 it). THIS is causing the undesired behavior.
>>
On Tuesday, December 4, 2018 at 1:40:03 PM UTC+5:30, Kamil Jońca wrote:
> Rusi Mody writes:
> > Best bet is switch to using systemd timers
>
> Second question: Why systemd kills my jobs? (Yes I know what parameters
> are responsible for this, but why they are configured that way?)
I am no
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 the undesired behavior.
>
> Dec
>> 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
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 cause to kill my jobs :(
>
> So my question is: is it safe
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
> systemd[1]:
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
Hi all!
Recently, when checking the "amavis" email account of my mail server,
I found several emails from the following cron jobs:
-
# cat /etc/cron.d/amavisd-new
#
# SpamAssassin maintenance for amavisd-new
#
# m
the current/last process id.
~
3) insert a line in your crontab file, to run 2)
~
You can check if a process is running by pars-, greping ps aux's output and
simply go monkey to finish some working script, but I am sure those needs aren't
just mine and there should be either a flag for cron jobs
~
of course, as part of this algorithm there should be a way of
determining if the job finished gracefully and there should be a way
of recontextualizing each restart ...
~
lbrtchx
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
script, but I am sure those needs
aren't
just mine and there should be either a flag for cron jobs, a utility, or some
best practices out there I don't know of. In fact, do you know of best
practices
for max data processing (I am talking here about jobs that may take days)
A 'crontab
Resolvi o problema em definitivo, vou compartilhar aqui para que fique
de referência futura.
Como dito, os scripts acionados pelo cron que façam uso do servidor X
precisam informar explicitamente as variáveis de ambiente DISPLAY e
XAUTHORITY.
No caso do DISPLAY, isto é trivial, basta escolher e
Consegui descobrir qual era o problema falando com o Javier
Fernandez-Sanguino, mantenedor do pacote cron do debian.
O script precisa acessar o servidor X e, para tanto, precisa do
XAUTHORITY correto. Quando executado da linha de comando, o XAUTHORITY
já está dado como variável do ambiente, mas
Olá,
Estou tentando, sem sucesso, agendar alguns scripts usando o cron e
gostaria de saber se alguém consegue me dar uma luz aqui.
Um dos scripts é:
#!/bin/bash
DATE=`date '+%Y%m%d_%H_%M'`
export DISPLAY=:0
/usr/bin/import -window root -resize 800
On Mon, Apr 9, 2012 at 15:20, Bob Proulx b...@proulx.com wrote:
Good. Can you log in as the non-root user?
No, all users on this box are from NIS.
Yes. Stop all other lines of debugging and focus on this issue. Why
is there an error there? Can you log in as that user?
Adam Mercer wrote:
Bob Proulx wrote:
Good. Can you log in as the non-root user?
No, all users on this box are from NIS.
How does having a user in NIS prevent you from logging in as that
user? Presumably the purpose of NIS is to enable the user to log into
the account. So I don't
On Wed, Apr 11, 2012 at 16:13, Bob Proulx b...@proulx.com wrote:
No, all users on this box are from NIS.
How does having a user in NIS prevent you from logging in as that
user? Presumably the purpose of NIS is to enable the user to log into
the account. So I don't understand this comment.
Hi
I am trying to connect to a squeeze VM as a standard user using ssh
keys, whenever I try to ssh into the box the connection is closed by
the VM:
ram@g5:~$ ssh -v lal-squeeze
OpenSSH_5.5p1 Debian-6+squeeze1, OpenSSL 0.9.8o 01 Jun 2010
debug1: Reading configuration data /etc/ssh/ssh_config
Adam Mercer wrote:
I am trying to connect to a squeeze VM as a standard user using ssh
keys, whenever I try to ssh into the box the connection is closed by
the VM:
ram@g5:~$ ssh -v lal-squeeze
Unfortunately this information is rarely useful. It is the *server*
side of the messages that are
Alexander Fortin wrote the following on 24.07.2008 23:09
/snip debug
hi
want to comment on the bugreport be my guest:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492307
--
bye Thilo
key: 0x4A411E09
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
On Jul 23, 6:50 pm, Andrei Popescu [EMAIL PROTECTED] wrote:
I partially agree with the useless of the feauture, but Debian
installer is asking if you want to allow root login or not, so I'm
Only in expert mode ;)
Uhm... well I always find difficult to define what a (Debian)
expert need
Alexander Fortin wrote the following on 24.07.2008 10:03
/snip
Yep, using usermod instead of passwd seems to work fine!
So, to report a bug or not to? Which mailing list?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389183
Alex
HTH
--
bye Thilo
key: 0x4A411E09
--
To UNSUBSCRIBE,
On Thu,24.Jul.08, 11:06:47, Thilo Six wrote:
Alexander Fortin wrote the following on 24.07.2008 10:03
/snip
Yep, using usermod instead of passwd seems to work fine!
So, to report a bug or not to? Which mailing list?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389183
Hi,
Andrei Popescu [EMAIL PROTECTED] writes:
Interesting, the manpage passwd(1) says that 'passwd -l' should also set
account expiry to 1, but it doesn't. Either passwd or the manpage is
wrong, so I think this should be reported against the package passwd.
It sets a value to 1 in my
Andrei Popescu wrote the following on 24.07.2008 18:28
/snip
--- man 1 passwd -
-l, --lock
Lock the named account. This option disables an account by changing
the password to a value which matches no possible encrypted value,
and by setting the
On Thu,24.Jul.08, 18:47:20, Thilo Six wrote:
well here it does. Tested with both Debian lenny and Ubuntu hardy.
Which version do you use?
I'm not the OP.
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
signature.asc
Description:
Andrei Popescu wrote the following on 24.07.2008 22:04
well here it does. Tested with both Debian lenny and Ubuntu hardy.
Which version do you use?
I'm not the OP.
Regards,
Andrei
I think that doesn't matter in this regard. You have said your passwd doesn't
behave as mentioned in the
On Thu,24.Jul.08, 22:35:01, Thilo Six wrote:
Andrei Popescu wrote the following on 24.07.2008 22:04
well here it does. Tested with both Debian lenny and Ubuntu hardy.
Which version do you use?
I'm not the OP.
Regards,
Andrei
I think that doesn't matter in this regard. You
On Jul 24, 6:50 pm, Thilo Six [EMAIL PROTECTED] wrote:
well here it does. Tested with both Debian lenny and Ubuntu hardy.
Which version do you use?
If you have a locked account without that expiry and use either of the above
just 'lock' that account again and then take a look at /etc/shadow.
A few days ago (due to a broken harddisk) I've installed Lenny from
scratch on my laptop.
I've copied pretty much every configuration from the old installation
(Etch) and everything seems good.
Well, everything but a couple of things: first of all, at install time
I chose no root login but only a
On Wed,23.Jul.08, 00:11:35, Alexander Fortin wrote:
[locked root account troubles]
Of course, I could unlock root account, but I thought it was good
practice to avoid root login from tty/ssh etc, and I'm pretty sure
this configuration was working well under Etch. Could this be
considered as
On Wed, 23 Jul 2008 13:10:26 +0300
Andrei Popescu [EMAIL PROTECTED] wrote:
On Wed,23.Jul.08, 00:11:35, Alexander Fortin wrote:
[locked root account troubles]
Of course, I could unlock root account, but I thought it was good
practice to avoid root login from tty/ssh etc, and I'm pretty
sure I'm not the only one on Lenny with locked root account and
root cron jobs running, and I still think this could lead to
confusion, especially if you were used to lock root accunt under Etch.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
if you want to allow root login or not, so I'm
Only in expert mode ;)
pretty sure I'm not the only one on Lenny with locked root account and
root cron jobs running, and I still think this could lead to
confusion, especially if you were used to lock root accunt under Etch.
I'm not an expert
On 2008-07-23 18:46 +0200, Andrei Popescu wrote:
I'm not an expert, but a quick read through passwd(1) says account
expiry should be set to '1', while your 'passwd -S' shows '-1', just
like a normal account.
How about trying to lock it again?
I tried that here, and it did not help.
On Wed, Mar 26, 2008 at 10:05:53AM -0400, Curt Howland wrote:
Well, yes, it works, but I get mail sent to me by cron explaining that
the job executed successfully.
I'd prefer not to get the mail. I don't get mail for any of the other
jobs in cron.daily, and I don't understand enough of
Hi,
I tried to whip up a small cron job, I put a short script
in /etc/cron.daily thinking that this would work.
Well, yes, it works, but I get mail sent to me by cron explaining that
the job executed successfully.
I'd prefer not to get the mail. I don't get mail for any of the other
jobs
Hi,
afaik cron (by default) mails all output from a script. If i create a
cronjob I usually dump all stdout (just redirect it to /dev/null)
But I want to be informed of any errors so I keep stderr.
example:
# this will get mailed
echo My cool cron script
# this will not mail stdout, but
On Wed, Mar 26, 2008 at 10:05 AM, Curt Howland [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I tried to whip up a small cron job, I put a short script
in /etc/cron.daily thinking that this would work.
Well, yes, it works, but I get mail sent to me by cron
-- Forwarded message --
From: Strong Cypher [EMAIL PROTECTED]
Date: Thu, 27 Mar 2008 09:13:54 +0100
Subject: Re: Silent Cron Jobs
To: Curt Howland [EMAIL PROTECTED]
your script need to drop any think from output to be able to drop mail sending
you have to redirect any command line
On Wed, 26 Mar 2008 20:40:12 +0100, Curt Howland wrote:
I tried to whip up a small cron job, I put a short script
in /etc/cron.daily thinking that this would work.
Well, yes, it works, but I get mail sent to me by cron explaining that
the job executed successfully.
better coordinated and elegant.
|
| Curt-
|
I send the output of such cron jobs to /dev/null.
that is
~ /dev/null 21
- --
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH6tcsu4tRirKTPYwRAuOGAJ9g3Xc6fZWKzZy4o
On 3/26/08, Curt Howland [EMAIL PROTECTED] wrote:
I tried to whip up a small cron job, I put a short script
in /etc/cron.daily thinking that this would work.
Well, yes, it works, but I get mail sent to me by cron explaining that
the job executed successfully.
That's odd, usually cron only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 27 March 2008, Patter [EMAIL PROTECTED] was heard to
say:
http://www.linuxhelp.net/guides/cron/
Thanks for all the help, everyone.
Indeed, for this, redirecting stderr is just fine too, so
cmd /dev/null 21
is exactly what I need.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I tried to whip up a small cron job, I put a short script
in /etc/cron.daily thinking that this would work.
Well, yes, it works, but I get mail sent to me by cron explaining that
the job executed successfully.
I'd prefer not to get the mail.
I'd like to use the continuation character \ in a cron job, but I get an
error when I do.
I use crontab -e to edit the crontab and have this sort of thing:
30 5 * * * script varable variable \
variable-text
when I try to save, I get this:
crontab: installing new crontab
On Sun, Oct 21, 2007 at 12:03:30PM -0700, David Liontooth wrote:
I'd like to use the continuation character \ in a cron job, but I get an
error when I do.
I use crontab -e to edit the crontab and have this sort of thing:
30 5 * * * script varable variable \
variable-text
when I
Rick Pasotto wrote:
On Sun, Oct 21, 2007 at 12:03:30PM -0700, David Liontooth wrote:
I'd like to use the continuation character \ in a cron job, but I get an
error when I do.
I use crontab -e to edit the crontab and have this sort of thing:
30 5 * * * script varable variable \
On Tue, Feb 27, 2007 at 12:13:11AM -0500 or thereabouts, Michael Pobega wrote:
I'm pretty new to cron jobs, and I've just started playing around with
them pretty recently.
Hi Michael:
Cool.
I'd like to be able to create a cron job that does a weekly archive of
all of my folders in ~/mail
On Tue, Feb 27, 2007 at 09:34:04AM -0500, Stephen wrote:
On Tue, Feb 27, 2007 at 12:13:11AM -0500 or thereabouts, Michael Pobega wrote:
I'd like to be able to create a cron job that does a weekly archive of
all of my folders in ~/mail. The way I have my mail set up is one
folder per box,
I'm pretty new to cron jobs, and I've just started playing around with
them pretty recently.
I'd like to be able to create a cron job that does a weekly archive of
all of my folders in ~/mail. The way I have my mail set up is one
folder per box, for example my folders are:
~/mail/inbox
~/mail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/07 23:13, Michael Pobega wrote:
I'm pretty new to cron jobs, and I've just started playing around with
them pretty recently.
I'd like to be able to create a cron job that does a weekly archive of
all of my folders in ~/mail. The way I
1 - 100 of 150 matches
Mail list logo
