From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Jason Molenda <jason-gcclist@molenda.com>
Cc: overseers@gcc.gnu.org, Matthias Klose <doko@cs.tu-berlin.de>
Subject: Re: Monthly mailing list archives: monthly-ml-tasks
Date: Sun, 18 Jul 2004 11:48:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.58.0407181346060.88645@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20040616144741.A95127@molenda.com>
On Wed, 16 Jun 2004, Jason Molenda wrote:
>> 5 6 1 * * cd /sourceware/infra/monthly-ml-tasks; exec ./DOIT.sh
>>
>> Indeed, this job is run on the first day of the month, at 6:05. Are
>> there any objections if I move this to 0:07?
> Unless I'm remembering incorrectly, there is a entry for root which
> HUPs apache a little while after the redirects/index pages have been
> updated. My guess is that the time of this crontab is related to
> that crontab.
Interestingly, it isn't really; the first rehup takes place before the
monthly-ml-tasks script is run:
#### Re-hup the daemon each month so that the new ml-redirects
#### can be loaded (cf infra/monthly-ml-tasks/update-http-redirects.sh)
####
#### This should run shortly after listarch's monthly list duty
#### script runs.
# Those scripts can take oddly long amounts of time to finish, so two
# extra rehups are here to ensure it gets done.
45 5,8,12 1 * * /sbin/service httpd reload>/dev/null
I have now moved the monthyl-ml-tasks script from 6:05 to 3:05, to reduce
the windows of "outdated-ness" that Matthias complained about...
> I'd recommend leaving some time between the two processes -- an hour
> say -- so that any mail archiving that is in the middle of happening
> has a chance to clear out. But that's just MHO. I purposefully wrote
> in the 6 hour delay originally out of laziness - I didn't want to think
> through the consequences of timing it closely and didn't think it really
> mattered if there was a gap of a few hours.
...so given what you wrote above, the root crontab now should be fine,
without changes?
Gerald
next prev parent reply other threads:[~2004-07-18 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 0:42 Gerald Pfeifer
2004-06-18 7:15 ` Jason Molenda
2004-07-18 11:48 ` Gerald Pfeifer [this message]
2004-07-19 9:38 ` Jason Molenda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.BSF.4.58.0407181346060.88645@acrux.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=doko@cs.tu-berlin.de \
--cc=jason-gcclist@molenda.com \
--cc=overseers@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).