[Bug 870694] New: excessive hourly cron job

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=870694

            Bug ID: 870694
        QA Contact: extras-qa at fedoraproject.org
          Severity: unspecified
           Version: rawhide
          Priority: unspecified
                CC: bos at serpentine.com,
                    haskell-devel at lists.fedoraproject.org,
                    petersen at redhat.com
          Assignee: petersen at redhat.com
           Summary: excessive hourly cron job
        Regression: ---
      Story Points: ---
    Classification: Fedora
                OS: Unspecified
          Reporter: pwouters at redhat.com
              Type: Bug
     Documentation: ---
          Hardware: Unspecified
        Mount Type: ---
            Status: NEW
         Component: ghc
           Product: Fedora

Description of problem:
ghc installs /etc/cron.hourly/ghc-doc-index. I find this problematic for
various reasons.

First, it seems this "documentation" can only come from package installs, so it
seems to be better places in an ghc spec macro or %post job.

Second, if there are really good reasons to keep this in, hourly is _way_ too
often. I would suggest weekly at most.

Third, it seemed to blow up for me too:

Date: Sat, 27 Oct 2012 20:01:02
From: Cron Daemon <root at bofh.nohats.ca>
To: root at bofh.nohats.ca
Subject: Cron <root at bofh> run-parts /etc/cron.hourly

/etc/cron.hourly/ghc-doc-index:

--read-interface=Cabal-1.14.0,Cabal-1.14.0/Cabal.haddock
--read-interface=array-0.4.0.0,array-0.4.0.0/array.haddock
--read-interface=base-4.5.0.0,base-4.5.0.0/base.haddock
--read-interface=bytestring-0.9.2.1,bytestring-0.9.2.1/bytestring.haddock
--read-interface=containers-0.4.2.1,containers-0.4.2.1/containers.haddock
--read-interface=deepseq-1.3.0.0,deepseq-1.3.0.0/deepseq.haddock
--read-interface=directory-1.1.0.2,directory-1.1.0.2/directory.haddock
--read-interface=filepath-1.3.0.0,filepath-1.3.0.0/filepath.haddock
--read-interface=ghc-prim-0.2.0.0,ghc-prim-0.2.0.0/ghc-prim.haddock
--read-interface=hashable-1.1.2.3,hashable-1.1.2.3/hashable.haddock
--read-interface=hashmap-1.0.0.2,hashmap-1.0.0.2/hashmap.haddock
--read-interface=integer-gmp-0.4.0.0,integer-gmp-0.4.0.0/integer-gmp.haddock
--read-interface=mtl-2.1.1,mtl-2.1.1/mtl.haddock
--read-interface=old-locale-1.0.0.4,old-locale-1.0.0.4/old-locale.haddock
--read-interface=old-time-1.1.0.0,old-time-1.1.0.0/old-time.haddock
--read-interface=parallel-3.2.0.2,parallel-3.2.0.2/parallel.haddock
--read-interface=parsec-3.1.2,parsec-3.1.2/parsec.haddock
--read-interface=pretty-1.1.1.0,pretty-1.1.1.0/pretty.haddock
--read-interface=process-1.1.0.1,process-1.1.0.1/process.haddock
--read-interface=text-0.11.2.0,text-0.11.2.0/text.haddock
--read-interface=transformers-0.3.0.0,transformers-0.3.0.0/transformers.haddock
--read-interface=unix-2.5.1.0,unix-2.5.1.0/unix.haddock
--read-interface=unordered-containers-0.2.1.0,unordered-containers-0.2.1.0/unordered-containers.haddock

In short, I would strongly suggest removing this cronjob altogether.

-- 
You are receiving this mail because:
You are on the CC list for the bug.