GNU bug report logs - #74395
'mumi send-email' fails to detect created issue number

Previous Next

Package: mumi;

Reported by: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Date: Sun, 17 Nov 2024 12:22:01 UTC

Severity: normal

Merged with 70879

Done: Arun Isaac <arunisaac <at> systemreboot.net>

Bug is archived. No further changes may be made.

Full log


Message #46 received at 74395 <at> debbugs.gnu.org (full text, mbox):

From: Arun Isaac <arunisaac <at> systemreboot.net>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 74395 <at> debbugs.gnu.org
Subject: Re: bug#74395: closed (Re: 'mumi send-email' fails to detect
 created issue number)
Date: Sun, 16 Mar 2025 16:47:45 +0000
Hi Maxim,

> Should we also raise the frequency of the rsync job? Currently it's
> every 5 minutes; we could make try perhaps every minute, but it should
> block when it's already running. I think the new Shepherd timer API
> would allow defining it as such.

Ah, good point! I didn't think of that. That would be worth doing to
further improve responsiveness.

Is there a way to prevent multiple rsync instances from running at the
same time? I understand it can be dangerous.
https://serverfault.com/questions/332577/is-it-safe-to-running-multiple-instances-of-rsync-together

Did you mean that the new Shepherd timer API has a way to achieve this
blocking?

Regards,
Arun




This bug report was last modified 60 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.