Github messages for voidlinux
 help / color / mirror / Atom feed
From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] `sysstat` blocks `fcron` running cron.hourly
Date: Wed, 27 Mar 2024 16:32:56 +0100	[thread overview]
Message-ID: <20240327153256.5B757217CA@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: 1079 bytes --]

Closed issue by Clos3y on void-packages repository

https://github.com/void-linux/void-packages/issues/49553

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.22_1 x86_64 AuthenticAMD notuptodate rrrmFFFF

### Package(s) Affected

sysstat-12.7.2_1, fcron-3.3.1_2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

No, not that I can see

### Expected behaviour

`fcron` runs all scripts in `/etc/cron.hourly`

### Actual behaviour

`fcron` runs all scripts alphabetically up to `sysstat`. This process does not terminate, locking `fcron` and preventing the execution of files starting with letters after 's' in `/etc/cron.hourly`.

### Steps to reproduce

0. Install `sysstat`, `fcron`, and setup the `fcron` service and systab crontab.
1. Create a script in `/etc/cron.hourly`.
2. If it comes before 'sysstat' alphabetically, it will be executed when the systab is set to run hourly. If it comes after, it will not execute until around fifty minutes after due to `sysstat` locking.

      parent reply	other threads:[~2024-03-27 15:32 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
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 ` leahneukirchen [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=20240327153256.5B757217CA@inbox.vuxu.org \
    --to=leahneukirchen@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).