From: Clos3y <Clos3y@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: `sysstat` blocks `fcron` running cron.hourly
Date: Wed, 27 Mar 2024 01:26:41 +0100 [thread overview]
Message-ID: <20240327002641.724E420FDB@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49553@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
New comment by Clos3y on void-packages repository
https://github.com/void-linux/void-packages/issues/49553#issuecomment-2021704997
Comment:
Hmm, adding `&` back in (and running `# fcrontab -z -u systab` followed by a reboot) doesn't fix the issue for me: it's still locked. `fcron` doesn't seem to care if you use `&`, it'll still lock. For example, I just tested
while true; do sleep 5; done &
in a test file in `/etc/cron.monthly`, reloaded the system crontab, and then forced `/etc/cron.monthly` to run with `fcrondyn`. `fcron` is still executing and is locked:
2024-03-27T00:20:08.44950 cron.notice: Mar 27 00:20:08 fcron[3843]: Job '/usr/bin/run-parts /etc/cron.monthly' started for user systab (pid 3844)
2024-03-27T00:20:46.30541 cron.warn: Mar 27 00:20:46 fcron[1022]: process already running: systab's '/usr/bin/run-parts /etc/cron.monthly'
Perhaps this is an `fcron` issue specifically?
next prev parent reply other threads:[~2024-03-27 0:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 18:53 [ISSUE] `sysstat` blocks `fcron` running `cron.hourly` Clos3y
2024-03-26 23:55 ` `sysstat` blocks `fcron` running cron.hourly classabbyamp
2024-03-27 0:26 ` Clos3y [this message]
2024-03-27 0:39 ` classabbyamp
2024-03-27 11:36 ` Clos3y
2024-03-27 12:09 ` Clos3y
2024-03-27 14:23 ` leahneukirchen
2024-03-27 14:24 ` leahneukirchen
2024-03-27 14:48 ` Clos3y
2024-03-27 14:49 ` leahneukirchen
2024-03-27 15:32 ` [ISSUE] [CLOSED] " leahneukirchen
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=20240327002641.724E420FDB@inbox.vuxu.org \
--to=clos3y@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).