From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sysstat cron jobs do not run with fcron
Date: Tue, 02 Apr 2024 18:22:04 +0200 [thread overview]
Message-ID: <20240402162204.2E02D21773@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49623@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/49623#issuecomment-2032507029
Comment:
The fact that `fcron` doesn't support `/etc/cron.d` is a design decision, not a bug. We ship crontab snippets as a convenience, but users are expected to either use a cron daemon that supports them or else implement their own preferred approach to periodic execution.
If running a script we didn't distribute clobbered the system crontab that runs the rest of the scripts in `/etc/cron.*`, restore the file from the package and be more careful about running such scripts in the future.
prev parent reply other threads:[~2024-04-02 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 12:04 [ISSUE] " ericjunkermann
2024-04-01 21:35 ` Clos3y
2024-04-02 16:22 ` [ISSUE] [CLOSED] " ahesford
2024-04-02 16:22 ` ahesford [this message]
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=20240402162204.2E02D21773@inbox.vuxu.org \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).