[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mageia-dev
Subject:    Re: [Mageia-dev] crond was not set to start
From:       Colin Guthrie <mageia () colin ! guthr ! ie>
Date:       2012-01-30 14:52:34
Message-ID: 4F26AEB2.9040907 () colin ! guthr ! ie
[Download RAW message or body]

'Twas brillig, and Olav Vitters at 29/01/12 20:34 did gyre and gimble:
> Yeah. Various services were broken after systemd switch. I enabled the
> broken ones. Have been using systemd for a few months at least. Suddenly
> crond broke.

I wonder if it suddenly got a native system unit rather than going via
sysvinit compatibility? That would have this kind of behaviour (assuming
it didn't break after the initial switch to systemd).

This is one of the cases I'm going to have to look at in the rpm-helper
scripts, but it should be doable.

Col

-- 

Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/
[prev in list] [next in list] [prev in thread] [next in thread]