[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#689304: marked as done (allow disabling of cron.daily)



Your message dated Fri, 09 Aug 2019 17:49:27 +0000
with message-id <E1hw915-00007j-7c@fasolo.debian.org>
and subject line Bug#689304: fixed in mdadm 4.1-3
has caused the Debian Bug report #689304,
regarding allow disabling of cron.daily
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
689304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689304
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: mdadm
Severity: wishlist

i intend to not run mdadm in monitor mode since i'm monitoring my system with other means, so i've disabled (by debconf) to run mdadm as daemon through sysvinit.

however, unrelated to that, mdadm *still* is run once a day through cron.daily, which is very annoying as the cronjob does not allow to be disabled in any admin friendly way.

please make the cronjob be disable'able through e.g. /etc/default/mdadm.

Regards,
Daniel

--
Address:        Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:          daniel.baumann@progress-technologies.net
Internet:       http://people.progress-technologies.net/~daniel.baumann/

--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 4.1-3

We believe that the bug you reported is fixed in the latest version of
mdadm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 689304@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Baumann <daniel.baumann@progress-linux.org> (supplier of updated mdadm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 09 Aug 2019 17:19:20 +0000
Source: mdadm
Architecture: source
Version: 4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Daniel Baumann <daniel.baumann@progress-linux.org>
Closes: 689304
Changes:
 mdadm (4.1-3) unstable; urgency=medium
 .
   * QA upload.
   * Adding debconf question to disable daily array scan (Closes: #689304):
     - if enabled (default), mdadm checks once a day for degraded arrays
       and missing spares to ensure that such events don't go unnoticed.
     - this is not useful when the system is part of an infrastructure
       with dedicated monitoring systems (e.g. icinga).
     - this debconf question makes it possible to disable these checks.
Checksums-Sha1:
 c950017628f98b58feb301846efcf6d0d272d3bb 1879 mdadm_4.1-3.dsc
 ca79c80d195319286e22ca874337959deb4a5ede 89640 mdadm_4.1-3.debian.tar.xz
 e5260c94f63081f91813cd2fb97ddc0c84b61819 5889 mdadm_4.1-3_amd64.buildinfo
Checksums-Sha256:
 3b9a09a0ecd7b108aefa12e16993c0de01f61bfe852af78754b1d5e053684fde 1879 mdadm_4.1-3.dsc
 dc83d00bcc8e44c47ae503168e82f551ed63f977a908861ab0adc1765f3af656 89640 mdadm_4.1-3.debian.tar.xz
 7265a748c9032ce8e306c73575607ead26bb6a5091621d8e7734b145cf2f01bf 5889 mdadm_4.1-3_amd64.buildinfo
Files:
 692e625c7f63e94dbb19adbe7638be46 1879 admin optional mdadm_4.1-3.dsc
 9cd4dee87f5538ffb45a1e39a4975ab9 89640 admin optional mdadm_4.1-3.debian.tar.xz
 478fd04e4abbb60d42fbe8a82c73a43c 5889 admin optional mdadm_4.1-3_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAl1NrOQACgkQVc8b+Yar
uceOJg//Xh7GL1M5xU8tJWFy9aORqPuojcMidgWz1XtkwBlJPiPF17CUHB8dH+W5
Hn/CyfLNZ3JLJ2xaTlZvn6KC5C6yIUSEQ7W8wynSlU2Z+rOPtW0X3PucxoNAV2eD
aznY2eFGfpKFDt88HjMLf8Q1bPIels5LFhNiJ7g6pmjHXgJ/H/pUJXbr1FM+OqvR
2VCowMvkcW1jGdTfj4KLCr4B5dTYQUB4++PHb/SHtLSSzP7SVFrt9VtoE/sTjRIh
JW327r2S4xKP+P0dqZJAQLgqzU1DymzynfyILuWxoMQUKDa1REHlVU80K20Ex7nb
GCi/wxImTAIBH3DqEHhEVmqM+EYj6BJKZ2sn2zzXE0h+OUy9oJVbbUHnon94R6pD
ZTaY9w2wifyvziSjzKl8vax6j/eztz1XisoWiThmZDlXDwwIW1F2ELMiVXSoSODE
nmllYFu1c8qvzFf4ZGJ4hFq2tGm8uk69elHN3UOTk3VCDPlkb083NsTDPjCUGLl9
ntUtFbuoCn7LHPvbE1rbmTFSJQSv0OAnsGlZYSjsfBZWkSHbz/eoRD4lDdqMswTn
46B6BJWgpVyS8yh2+pYyu3FcRfLKBAgZx9hoJwqF+RyziQyJWUyRnb5kxSsnHgid
jVxMwUb/pBk9MHNgW10qJD6i35X4OVqAU31q2xlBIWKqX3duiuM=
=d47l
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: