From: boyd.roberts@ca-indosuez.com
To: 9fans@cse.psu.edu
Subject: Réf. : Réf. : Réf. : [9fans] Auth & cron
Date: Tue, 18 Jul 2000 18:24:11 +0200 [thread overview]
Message-ID: <41256920.005FE4BB.00@SNPAR12.> (raw)
What I don't like is
1: rebooting your cpu server makes your cron die and forget your
entries.
(a workaround would be to check that it is running when you log in,
and spawn a new cron otherwise; but that's not a fix).
yup, that's the _problem_.
reply other threads:[~2000-07-18 16:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41256920.005FE4BB.00@SNPAR12. \
--to=boyd.roberts@ca-indosuez.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).