I am using parallel-20190922-1 from epel and when I run a job in
cron such as /usr/bin/parallel /usr/bin/bash ::: a.sh b.sh c.sh
I don't receive any mail regardless of all three scripts generating
output.
All other jobs in cron generate mail if they write to stdout or stderr.
When the above is
On Mon, Nov 18, 2019 at 10:50:57AM +, John Horne wrote:
> Sorry, I should have been more clear. I'm not looking for a 'per-script'
> solution. Logging when a job starts is performed by crond, so logging when it
> ends should also be done by crond.
For what it's worth, you'll see entries in
On Fri, 2019-11-15 at 16:32 -0500, Karl Vogel wrote:
> > > On Fri, Nov 15, 2019 at 05:54:07PM +, John Horne wrote:
>
> J> In trying to resolve a problem with a cron job, we can see when the job
> J> starts by looking in the /var/log/cron log file. However, I was asked if
> J> when the job
Hallo,
I think the right way is to add logging into the script with all details for
debug and and monitoring.
Ralf
Von meinem iPhone gesendet
> Am 15.11.2019 um 18:55 schrieb John Horne :
>
> Hello,
>
> In trying to resolve a problem with a cron job, we can see when the job starts
> by
Hello,
In trying to resolve a problem with a cron job, we can see when the job starts
by looking in the /var/log/cron log file. However, I was asked if when the job
ends could also be logged. (It seems to be something that crops up every so
often over the years.)
I found on the 'net this article
On Thu, July 20, 2017 12:30 pm, Alexander Dalloz wrote:
> Am 20.07.2017 um 16:57 schrieb Valeri Galtsev:
>> ( and don't forget to: newaliases && postfix reload )
>
> There is no need to reload Postfix after aliases_db changes and a
> newaliases. Same applies for other hashed maps refreshed by
Am 20.07.2017 um 16:57 schrieb Valeri Galtsev:
( and don't forget to: newaliases && postfix reload )
There is no need to reload Postfix after aliases_db changes and a
newaliases. Same applies for other hashed maps refreshed by postmap.
Alexander
On 07/20/2017 01:03 AM, isdtor wrote:
postfix only uses the aliases map for local delivery. If the recipient email
address is fully qualified, local delivery is not even in the picture ...
postfix is not the problem here as the log shows
... to=, orig_to= ...
I read it the
On Thu, July 20, 2017 8:54 am, Richard wrote:
>
>> Date: Thursday, July 20, 2017 02:25:52 +
>> From: Richard
>>
>>> Date: Wednesday, July 19, 2017 23:31:10 +
>>> From: Chad Cordero
>>>
>>> Itâs being rejected before it even
> Date: Thursday, July 20, 2017 14:26:49 +
> From: Chad Cordero
>
>> From: CentOS on behalf of Richard
>> Date: Thursday, July 20, 2017 at 6:54 AM
>>
>> The "mailto" value is crontab file specific, so setting it in
>> /etc/crontab would only
of Richard
<lists-cen...@listmail.innovate.net>
Reply-To: CentOS mailing list <centos@centos.org>
Date: Thursday, July 20, 2017 at 6:54 AM
To: CentOS mailing list <centos@centos.org>
Subject: Re: [CentOS] Cron sending to root after changing MAILTO
Date: Thursday, July 2
> Date: Thursday, July 20, 2017 02:25:52 +
> From: Richard
>
>> Date: Wednesday, July 19, 2017 23:31:10 +
>> From: Chad Cordero
>>
>> It’s being rejected before it even reaches the mailbox, so
>> forwarding won’t work. Crond
> Date: Thursday, July 20, 2017 09:02:02 +0100
> From: Pete Biggs
>
> On Wed, 2017-07-19 at 23:31 +, Chad Cordero wrote:
>> It’s being rejected before it even reaches the mailbox, so
>> forwarding won’t work. Crond should really be using the MAILTO
>> variable and it’s
On Wed, 2017-07-19 at 23:31 +, Chad Cordero wrote:
> It’s being rejected before it even reaches the mailbox, so forwarding
> won’t work. Crond should really be using the MAILTO variable and
> it’s not.
>
Have you restarted crond after you made the changes?
P.
> Best is to define a mail alias for the root user. That way you have it
> defined at a single place for all occurances of mail destined to root.
postfix only uses the aliases map for local delivery. If the recipient email
address is fully qualified, local delivery is not even in the picture
> Date: Wednesday, July 19, 2017 23:31:10 +
> From: Chad Cordero
>
> It’s being rejected before it even reaches the mailbox, so
> forwarding won’t work. Crond should really be using the MAILTO
> variable and it’s not.
>
In my testing, this worked as advertised.
On Wed, 2017-07-19 at 23:31 +, Chad Cordero wrote:
> It’s being rejected before it even reaches the mailbox
Is it rejected because of the recipient address or the sender address?
In your log message, I noticed this sender address:
from=
In case your mail server is
On 07/19/2017 02:42 PM, Chad Cordero wrote:
I have “root:ecssupp...@csusb.edu” in my /etc/aliases file already.
Did you run "newaliases"?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
ng list <centos@centos.org>
Date: Wednesday, July 19, 2017 at 4:13 PM
To: CentOS mailing list <centos@centos.org>
Subject: Re: [CentOS] Cron sending to root after changing MAILTO
- Original Message -
From: "CentOS mailing list"
To:"CentOS mailing list&
Am 20.07.2017 um 00:36 schrieb Chad Cordero:
Ah. Here you go.
It would be nice if you would avoid TOFU posting (top-posting and full
quoting).
# grep A5077100E776C /var/log/maillog
Jul 19 13:15:55 mailcampaign1 postfix/pickup[19675]: A5077100E776C: uid=0
from=
Jul 19 13:15:55
- Original Message -
From: "CentOS mailing list"
To:"CentOS mailing list"
Cc:
Sent:Wed, 19 Jul 2017 20:46:21 +0000
Subject:[CentOS] Cron sending to root after changing MAILTO
I am running CentOS 7 on an outbound gateway server running
Postfix. I have a c
ting it from your computer.
From: CentOS <centos-boun...@centos.org> on behalf of Alexander Dalloz
<ad+li...@uni-x.org>
Reply-To: CentOS mailing list <centos@centos.org>
Date: Wednesday, July 19, 2017 at 3:15 PM
To: "centos@centos.org" <centos@centos.org>
Subject: R
Am 20.07.2017 um 00:03 schrieb Chad Cordero:
Here is the last one I got. As you can see it was send tor...@csusb.edu, a
restricted distribution group, not obeying /etc/aliases or MAILTO definition in
crontab.
Speaking about log content I meant to show the trace of the relayed mail
in the
ly 19, 2017 at 2:49 PM
To: "centos@centos.org" <centos@centos.org>
Subject: Re: [CentOS] Cron sending to root after changing MAILTO
Am 19.07.2017 um 23:42 schrieb Chad Cordero:
I have “root:ecssupp...@csusb.edu” in my /etc/aliases file already.
Chad Cordero
Then please pro
Am 19.07.2017 um 23:42 schrieb Chad Cordero:
I have “root:ecssupp...@csusb.edu” in my /etc/aliases file already.
Chad Cordero
Then please provide log information about the mails to root being
relayed to your Exchange host.
Alexander
___
CentOS
;centos@centos.org" <centos@centos.org>
Subject: Re: [CentOS] Cron sending to root after changing MAILTO
Am 19.07.2017 um 22:46 schrieb Chad Cordero:
I am running CentOS 7 on an outbound gateway server running Postfix. I have a
couple of cron jobs I was expecting to see in my emai
Am 19.07.2017 um 22:46 schrieb Chad Cordero:
I am running CentOS 7 on an outbound gateway server running Postfix. I have a
couple of cron jobs I was expecting to see in my email that never showed up.
It turns out that they were delivered to root, which is restricted on our
exchange server,
I am running CentOS 7 on an outbound gateway server running Postfix. I have a
couple of cron jobs I was expecting to see in my email that never showed up.
It turns out that they were delivered to root, which is restricted on our
exchange server, instead of the address I defined. Please help.
[snip]
> The script works find from the command line, but will not work at all
> in a cron job.
This almost always points to something in the environment.
Where did Astro::Time actually get installed? Check the above paths to
see if it is actually there, or whether cpan put it somewhere
On 2017-01-02, Gregory P. Ennis wrote:
>
> The error message I get in the logs is :
>
> Can't locate Astro/Time.pm in @INC (@INC contains:
> /usr/local/lib64/perl5 /usr/local/share/perl5
> /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl
> /usr/lib64/perl5
Everyone,
I am building a gateway server with a new : CentOS Linux release
7.3.1611 (Core) with 3.10.0-514.2.2.el7.x86_64 kernel.
Everything was going find, but I was not able to get a particular
cronjob to function properly that contained a perl script with
Astro::Time as an include file.
After many hours of struggling with it, i did "crontab -u nobody -e" and
put the same line in private nobody's crontab. Looks like it's working.
Don't know why and how.
--
Over And Out
MoonWolf
___
CentOS mailing list
CentOS@centos.org
If your script is failing, I would normally expect it to output some error
messages. Cron will email this to root by default. Maybe check
/var/spool/mail/root? Or set MAILTO="youremail address" at the top of your
cron script.
___
CentOS mailing list
On 23 April 2016 at 10:25, Marcin Trendota wrote:
> Anything interesting in the logs?
> >
> > sudo journalctl -xf _SYSTEMD_UNIT=crond.service
>
> Don't know.
>
> [root@kohrin cron.d]# sudo journalctl -xf _SYSTEMD_UNIT=crond.service
>
...
> (/etc/cron.d/osticket-cron)
>
On 4/22/2016 5:27 PM, Marcin Trendota wrote:
On Friday 22 of April 2016 8:10:04 PM Steven Ford wrote:
>Seemed strange is all. Can the nobody user read down into
>/var/www/html/osticket/api? If it works in tmp, maybe permissions are
>the issue.
As i said. sudo works as a charm. Cron rebels...
On Friday 22 of April 2016 8:10:04 PM Steven Ford wrote:
> Seemed strange is all. Can the nobody user read down into
> /var/www/html/osticket/api? If it works in tmp, maybe permissions are
> the issue.
As i said. sudo works as a charm. Cron rebels...
--
Over And Out
MoonWolf
On Saturday 23 of April 2016 10:08:54 AM Kahlil Hodgson wrote:
> Anything interesting in the logs?
>
> sudo journalctl -xf _SYSTEMD_UNIT=crond.service
Don't know.
[root@kohrin cron.d]# sudo journalctl -xf _SYSTEMD_UNIT=crond.service
-- Logs begin at śro 2015-12-02 22:34:16 CET. --
kwi 22
Seemed strange is all. Can the nobody user read down into
/var/www/html/osticket/api? If it works in tmp, maybe permissions are the
issue.
On Apr 22, 2016 7:57 PM, "Marcin Trendota" wrote:
> On Friday 22 of April 2016 5:58:39 PM Steven Ford wrote:
> > Why bother with */1?
Anything interesting in the logs?
sudo journalctl -xf _SYSTEMD_UNIT=crond.service
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
On Friday 22 of April 2016 5:58:39 PM Steven Ford wrote:
> Why bother with */1? Wouldn't that be the same as just *?
That's for debugging. It'll be */5 for production purposes.
Anyway. It still doesn't work. Why?
--
Over And Out
MoonWolf
___
CentOS
On Fri, Apr 22, 2016 at 05:58:39PM -0400, Steven Ford wrote:
> Why bother with */1? Wouldn't that be the same as just *?
> On Apr 22, 2016 5:48 PM, "Marcin Trendota" wrote:
>
I had the same question. Plus, the man page says "'/' specifies
skips of the number's value
Why bother with */1? Wouldn't that be the same as just *?
On Apr 22, 2016 5:48 PM, "Marcin Trendota" wrote:
> On Friday 22 of April 2016 11:40:33 PM Marcin Trendota wrote:
> > What the heck is wrong with cron?
> >
> > */1 * * * * nobody /usr/bin/php
On Friday 22 of April 2016 11:40:33 PM Marcin Trendota wrote:
> What the heck is wrong with cron?
>
> */1 * * * * nobody /usr/bin/php /var/www/html/osticket/api/cron.php
>
> in /etc/cron.d doesn't get executed at all (ran from console works of
> course!). But the SAME file in /tmp runs
What the heck is wrong with cron?
*/1 * * * * nobody /usr/bin/php /var/www/html/osticket/api/cron.php
in /etc/cron.d doesn't get executed at all (ran from console works of
course!). But the SAME file in /tmp runs flawlessly:
*/1 * * * * nobody /usr/bin/php /tmp/cron.php
It's CentOS7 on VPS
Check selinux context for directory?
This is Centos 7 minimal running in an openvz container. As far as I
can tell selinux is not present. sestatus returns command not found.
I have noanacron installed on a fresh centos 7 install.
I added this too settings.
nano /etc/cron.d/0hourly
I have noanacron installed on a fresh centos 7 install.
I added this too settings.
nano /etc/cron.d/0hourly
*/5 * * * * root run-parts /etc/cron.fiveminutes
*/1 * * * * root run-parts /etc/cron.minute
0,30 * * * * root run-parts /etc/cron.halfhour
and then created the directories for it. Now
Check selinux context for directory?
30.4.2015 12.19 ap. Matt matt.mailingli...@gmail.com kirjoitti:
I have noanacron installed on a fresh centos 7 install.
I added this too settings.
nano /etc/cron.d/0hourly
*/5 * * * * root run-parts /etc/cron.fiveminutes
*/1 * * * * root run-parts
Do you need cron installed for the files in /etc/cron.daily/ to
execute? Did a Centos 6.x minimal openvz install and noticed cron is
not installed by default and after installing mlocate cant help but
wander if it will be updated without it.
___
CentOS
Hello Matt,
On Mon, 28 Jul 2014 14:14:53 -0500 Matt matt.mailingli...@gmail.com wrote:
Do you need cron installed for the files in /etc/cron.daily/ to
execute? Did a Centos 6.x minimal openvz install and noticed cron is
not installed by default and after installing mlocate cant help but
CentOS-6.2
We moved a cron job from a CentOS-5.7 host to a CentOS-6.2
host. The MAILTO variable is set to supp...@harte-lyne.ca
in both instances. On the CentOS-6 host instead of
receiving the mail with the output we see this in
/var/log/cron instead:
Mar 12 14:49:01 inet09 CROND[6639]: (cron
On Mar 12, 2012, at 12:03 PM, James B. Byrne wrote:
CentOS-6.2
We moved a cron job from a CentOS-5.7 host to a CentOS-6.2
host. The MAILTO variable is set to supp...@harte-lyne.ca
in both instances. On the CentOS-6 host instead of
receiving the mail with the output we see this in
Am 12.03.2012 20:03, schrieb James B. Byrne:
CentOS-6.2
We moved a cron job from a CentOS-5.7 host to a CentOS-6.2
host. The MAILTO variable is set to supp...@harte-lyne.ca
in both instances. On the CentOS-6 host instead of
receiving the mail with the output we see this in
/var/log/cron
On Mar 12, 2012, at 12:03 PM, James B. Byrne wrote:
/ CentOS-6.2
//
// We moved a cron job from a CentOS-5.7 host to a CentOS-6.2
// host. The MAILTO variable is set tosupport at harte-lyne.ca
http://lists.centos.org/mailman/listinfo/centos
// in both instances. On the CentOS-6 host
On 3/4/2012 10:25 PM, Tim Dunphy wrote:
hello list,
I am attempting to backup a centos 5.4 (x86_64) server running mysql
with a cron job. Here's how the cron job looks:
[root@cloud:/home/bluethundr/backupdb] #crontab -l
* 3 * * * /usr/bin/mysqldump jfwiki
Am 06.03.2012 18:56, schrieb Bowie Bailey:
On 3/4/2012 10:25 PM, Tim Dunphy wrote:
hello list,
I am attempting to backup a centos 5.4 (x86_64) server running mysql
with a cron job. Here's how the cron job looks:
[root@cloud:/home/bluethundr/backupdb] #crontab -l
* 3 * * *
Am 05.03.2012 04:25, schrieb Tim Dunphy:
hello list,
I am attempting to backup a centos 5.4 (x86_64) server running mysql
with a cron job. Here's how the cron job looks:
[root@cloud:/home/bluethundr/backupdb] #crontab -l
* 3 * * * /usr/bin/mysqldump jfwiki
From: Tim Dunphy bluethu...@gmail.com
To: CentOS mailing list centos@centos.org
Sent: Sunday, March 4, 2012 8:25 PM
Subject: [CentOS] cron job not running
hello list,
I am attempting to backup a centos 5.4 (x86_64) server running mysql with a
cron job
On Sun, Mar 4, 2012 at 9:25 PM, Tim Dunphy bluethu...@gmail.com wrote:
hello list,
I am attempting to backup a centos 5.4 (x86_64) server running mysql
with a cron job. Here's how the cron job looks:
[root@cloud:/home/bluethundr/backupdb] #crontab -l
* 3 * * * /usr/bin/mysqldump jfwiki
hello list,
I am attempting to backup a centos 5.4 (x86_64) server running mysql
with a cron job. Here's how the cron job looks:
[root@cloud:/home/bluethundr/backupdb] #crontab -l
* 3 * * * /usr/bin/mysqldump jfwiki
/home/bluethundr/backupdb/wiki-$(date +%Y%m%d).sql
However if I run the
On Sun, Jul 31, 2011 at 3:31 PM, John R. Dennison j...@gerdesas.com wrote:
On Sun, Jul 31, 2011 at 03:19:01PM +1200, Cliff Pratt wrote:
Tim, the program is run by cron in a different environment to the
standard online environment. Is /bin/alldb a script? If so, *any*
program in the script
On Sun, 31 Jul 2011, Cliff Pratt wrote:
To: CentOS mailing list centos@centos.org
From: Cliff Pratt enkiduonthe...@gmail.com
Subject: Re: [CentOS] cron jobs not running
On Sun, Jul 31, 2011 at 3:31 PM, John R. Dennison j...@gerdesas.com wrote:
On Sun, Jul 31, 2011 at 03:19:01PM +1200
On Sun, 31 Jul 2011, Keith Roberts wrote:
Woops! I meant Tim the OP - not Cliff :)
Cliff - you might like to check out my customizable mysql
database backup script (PHP5 CLI code) at:
http://forums.fedoraforum.org/showpost.php?p=1499959postcount=3
Kind Regards,
Keith Roberts
Hello Tim,
On Sun, 2011-07-31 at 03:07 +, Tim Dunphy wrote:
* * * * * /bin/alldb
/home/bluethundr/backupdb/alldb-$(date +%Y%m%d%H%S).sql
Jul 30 22:59:01 VIRTCENT09 crond[8007]: (root) CMD (/bin/alldb
/home/bluethundr/backupdb/alldb-$(date +)
Think you need
On 07/30/2011 10:07 PM, Tim Dunphy wrote:
hello list!!
I'm attempting to find out why this cron job isn't running. the host is
centos 5.6 on i386 just so you know.
0 3 * * * /bin/alldb
/home/bluethundr/backupdb/alldb-$(date +%Y%m%d%H%S).sql
However I do
hello list!!
I'm attempting to find out why this cron job isn't running. the host is centos
5.6 on i386 just so you know.
0 3 * * * /bin/alldb
/home/bluethundr/backupdb/alldb-$(date +%Y%m%d%H%S).sql
The job is meant to backup all the databases on a mysql
On Sun, Jul 31, 2011 at 3:07 PM, Tim Dunphy bluethu...@jokefire.com wrote:
hello list!!
I'm attempting to find out why this cron job isn't running. the host is
centos 5.6 on i386 just so you know.
0 3 * * * /bin/alldb
/home/bluethundr/backupdb/alldb-$(date
On 07/30/2011 11:07 PM, Tim Dunphy wrote:
03***/bin/alldb /home/bluethundr/backupdb/alldb-$(date
+%Y%m%d%H%S).sql
I think the date paremters (percent etc) is causing you problems here.
Try it simple first:
* * * * */bin/alldb
On Sun, Jul 31, 2011 at 03:19:01PM +1200, Cliff Pratt wrote:
Tim, the program is run by cron in a different environment to the
standard online environment. Is /bin/alldb a script? If so, *any*
program in the script should have a full path, or the PATH enviroment
variable should be specified
Hello ,
identical PHP script on two CentOS 5.6 (i386 and x86_64) gives the following
information while running as a cron job.
Warning: Terminal locale not UTF-8, but UTF-8 locale is being forced.
Screen output may not be correctly printed
--
Best regards,
Armin
Check the local in both machines and look under /var/log/ for clues.
Armin Tueting armin.tuet...@tueting-online.com 7/19/2011 10:49 AM
Hello ,
identical PHP script on two CentOS 5.6 (i386 and x86_64) gives the following
information while running as a cron job.
Warning: Terminal locale
Title: Re: [CentOS] Cron questions
Hello Lisandro,
Tuesday, July 19, 2011, 4:52:28 PM, you wrote:
Check the local in both machines and look under /var/log/ for clues.
Armin Tueting armin.tuet...@tueting-online.com 7/19/2011 10:49 AM
Hello ,
identical PHP script on two CentOS 5.6 (i386
hey centos
long time no hear! :) I'm having a small issue where the backup jobs
that I set to run in the crontab of the backup user do not appear to
be running. Here's how I set it up (with crontab -e as the backup
user):
run amanda every night (check at 2:45 and backup at 3)
45 2 * * *
sorry forgot to mention that cron IS running
r...@amanda init.d]# ps -ef | grep cron
root 13686 1 0 07:18 ?00:00:00 crond
root 13771 6676 0 07:34 pts/200:00:00 grep cron
On Wed, Jan 5, 2011 at 7:29 AM, bluethundr bluethu...@gmail.com wrote:
hey centos
long time no
hey centos
long time no hear! :) I'm having a small issue where the backup jobs
that I set to run in the crontab of the backup user do not appear to
be running. Here's how I set it up (with crontab -e as the backup
user):
run amanda every night (check at 2:45 and backup at 3)
45 2 * *
On Wed, Jan 05, 2011 at 10:29:52AM -0500, Mike Burger wrote:
hey centos
long time no hear! :) I'm having a small issue where the backup jobs
that I set to run in the crontab of the backup user do not appear to
be running. Here's how I set it up (with crontab -e as the backup
user):
Hi,
On Wed, 2011-01-05 at 07:29 -0500, bluethundr wrote:
[amandabac...@amanda ~]$ ls -l /usr/sbin/amcheck
-rwsr-x--- 1 root disk 68624 Dec 29 14:08 /usr/sbin/amcheck
Unless the backup user is in the disk group it has no permissions on
this file.
Although I'm not sure what the 's' indicates
On 1/5/2011 6:35 AM, bluethundr wrote:
sorry forgot to mention that cron IS running
45 2 * * * /usr/sbin/amcheck /var/log/amanda/crontab/amcheck.log
* 3 * * * /usr/sbin/amdump /var/log/amanda/crontab/amdump.log
And here's a tail of the cron logs
[r...@amanda init.d]# tail
Hi
When I enable a box to do authentication using LDAP it breaks cron for users
like jboss.
I get the following in /var/log/secure
Sep 14 15:25:01 exoipatest01 crond[7214]: pam_access(crond:account): access
denied for user `jboss' from `cron'
I have the following in /etc/ldap.conf
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
Behalf Of Gerrard Geldenhuis
Sent: 14 September 2010 16:28
To: centos@centos.org
Subject: [CentOS] cron breaking when enabling ldap
Hi
When I enable a box to do authentication using LDAP
On 03/30/2010 11:45 PM, Joseph L. Casale wrote:
I know the cron script can check for node status, but then I have multiple
copies to maintain wheres my existing resources all reference config on the
shard fs (httpd/sql etc) so a change on the active node makes that permanent
on the next node.
I dont quite get clearly what it is that you are looking to achieve
here, but rather than cron - have you considered a more adept job
scheduling / orchestrating tool ? there are some very nicely done open
source ones out there.
I have a filesystem that mounts only on the active node of an
On Tue, 2010-04-06 at 11:10 +, Joseph L. Casale wrote:
I dont quite get clearly what it is that you are looking to achieve
here, but rather than cron - have you considered a more adept job
scheduling / orchestrating tool ? there are some very nicely done open
source ones out there.
On 04/06/2010 12:10 PM, Joseph L. Casale wrote:
I have an interim solution while I research, do you have any personal
reco's for job scheduling daemons?
For what you have in mind, I'd have thought going with either
supervisord or torque would be ideal.
or as John pointed out, you could go
I need an idea on how to accomplish this: I have a cluster that I only want
to run cron jobs on when its active.
I know the cron script can check for node status, but then I have multiple
copies to maintain wheres my existing resources all reference config on the
shard fs (httpd/sql etc) so a
Joseph L. Casale wrote:
I need an idea on how to accomplish this: I have a cluster that I only want
to run cron jobs on when its active.
What kind of cluster? the term cluster can mean almost
anything these days.
nate
___
CentOS mailing list
What kind of cluster? the term cluster can mean almost
anything these days.
Sorry, my bad. RHCS
Thanks,
jlc
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
On Wed, 2010-03-31 at 00:33 +, Joseph L. Casale wrote:
What kind of cluster? the term cluster can mean almost
anything these days.
Sorry, my bad. RHCS
I can tell you how I did it for a 2-node heartbeat cluster. I enabled
the cron jobs on both servers, and had the following snippet at
From: Timothy Murphy gayle...@eircom.net
The scripts in /etc/cron.d/ all run fine,
but those in /etc/cron.hourly, etc, seem to be ignored.
Tried:
printf #'!'/bin/bash\ntouch /tmp/cron.test\n
/etc/cron.hourly/cront.test; chmod 755 /etc/cron.hourly/cront.test
Next hour:
$ ll /tmp/cron.test
I've just noticed that cron.daily, etc,
do not seem to be running on my CentOS-5.4 system.
The scripts in /etc/cron.d/ all run fine,
but those in /etc/cron.hourly, etc, seem to be ignored.
I see that according to /var/log/cron
these commands are seen, eg
Feb 28 18:01:01 helen crond[6680]: (root)
On 02/28/2010 01:00 PM, Timothy Murphy wrote:
I've just noticed that cron.daily, etc,
do not seem to be running on my CentOS-5.4 system.
The scripts in /etc/cron.d/ all run fine,
but those in /etc/cron.hourly, etc, seem to be ignored.
I see that according to /var/log/cron
these commands are
We have CENTOS 5.3 on DELL server. there has a cron job supposedly should run
on 1st and 3rd week on Saturday but it run everyday. anyone know what wrong?
01 08 1-7,15-21 * 6 program.sh
___
您的生活即時通 - 溝通、娛樂、生活、工作一次搞定!
This was just recently
2010/1/7 mcclnx mcc mcc...@yahoo.com.tw:
We have CENTOS 5.3 on DELL server. there has a cron job supposedly should
run on 1st and 3rd week on Saturday but it run everyday. anyone know what
wrong?
This was just covered recently in another mail thread with loads of
2010/1/7 mcclnx mcc mcc...@yahoo.com.tw:
We have CENTOS 5.3 on DELL server. there has a cron job supposedly should
run on 1st and 3rd week on Saturday but it run everyday. anyone know what
wrong?
01 08 1-7,15-21 * 6 program.sh
From man 5 crontab
The time and date fields are:
Hi,
On Mon, 2009-12-14 at 08:51 +0100, Michel van Deventer wrote:
Hi,
On Mon, 2009-12-14 at 09:46 +0200, Roland Roland wrote:
Hello,
i have a certain issue at hand that i'm trying to solve.
there's a certain command that i need to execute 10 minutes after boot.
how can i set
On Mon, Dec 14, 2009 at 2:46 AM, Roland Roland r_o_l_a_...@hotmail.com wrote:
Hello,
i have a certain issue at hand that i'm trying to solve.
there's a certain command that i need to execute 10 minutes after boot.
how can i set that? im not very expert with cron jobs but can it be done
that
On Mon, Dec 14, 2009 at 12:39:50PM -0500, Brian Mathis wrote:
On Mon, Dec 14, 2009 at 2:46 AM, Roland Roland r_o_l_a_...@hotmail.com
wrote:
Hello,
i have a certain issue at hand that i'm trying to solve.
there's a certain command that i need to execute 10 minutes after boot.
how can
Hello,
i have a certain issue at hand that i'm trying to solve.
there's a certain command that i need to execute 10 minutes after boot.
how can i set that? im not very expert with cron jobs but can it be done
that way? i know that cronjob works on specified time but how can i set
it to run
Hi,
On Mon, 2009-12-14 at 09:46 +0200, Roland Roland wrote:
Hello,
i have a certain issue at hand that i'm trying to solve.
there's a certain command that i need to execute 10 minutes after boot.
how can i set that? im not very expert with cron jobs but can it be done
that way? i know
Roland Roland wrote:
Hello,
i have a certain issue at hand that i'm trying to solve.
there's a certain command that i need to execute 10 minutes after boot.
how can i set that? im not very expert with cron jobs but can it be done
that way? i know that cronjob works on specified time but
Quoting Roland Roland r_o_l_a_...@hotmail.com:
Hello,
i have a certain issue at hand that i'm trying to solve.
there's a certain command that i need to execute 10 minutes after boot.
how can i set that? im not very expert with cron jobs but can it be done
that way? i know that cronjob
1 - 100 of 128 matches
Mail list logo