Changes to mcron service not applied after home reconfiguration

  • Done
  • quality assurance status badge
Details
2 participants
  • Fabio Natali
  • Bruno Victal
Owner
unassigned
Submitted by
Fabio Natali
Severity
normal

Debbugs page

Fabio Natali wrote 2 years ago
(address . bug-guix@gnu.org)
87o7uy9pfz.fsf@reckondigital.com
Dear All,

My Guix Home configuration includes a Mcron service along the lines of:

,----
| (define my/home-mcron-service
| (service
| home-mcron-service-type
| (home-mcron-configuration
| (jobs
| (list
| #~(job
| '(next-minute)
| (lambda () (system* "notmuch" "new"))
| "Get new email and process it via the Notmuch hook scripts."))))))
`----

After updating the above snippet in my `home-config.scm' and launching a
home-reconfiguration, I noticed that the mcron changes had not been
picked up.

For instance, `herd schedule mcron' prints information that's clearly
related to the previous job. A `herd restart mcron' also doesn't seem to
help.

The mcron job is finally picked up when restarting the system though,
which also seems to confirm the mcron job is ok, in itself.

I'll try and explore this a bit further later but I thought of opening a
bug as well. Anyone else having the same issue?

Thanks, best, Fabio.
Fabio Natali wrote 2 years ago
(address . 58166@debbugs.gnu.org)
87tu4og8zd.fsf@reckondigital.com
On 2022-09-29, 16:21:20 +0100, Fabio Natali wrote:
Toggle quote (4 lines)
> After updating the above snippet in my `home-config.scm' and launching
> a home-reconfiguration, I noticed that the mcron changes had not been
> picked up.

I stand corrected. Changes do seem to be picked up now. I'm no longer
able to reproduce this. Possibly solved after a recent upgrade. Thanks,
best, Fabio.
Bruno Victal wrote 2 years ago
control-msg
(name . control)(address . control@debbugs.gnu.org)
4e7e3d93-01e3-da95-fc0a-fc07dd7e0734@makinata.eu
close 58166
tag 62678 + security

quit
?
Your comment

This issue is archived.

To comment on this conversation send an email to 58166@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 58166
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help