On Thu, 2015-05-21 at 16:14 -0400, Tim St Clair wrote: > we had unit files in /etc/systemd/system which were explicit over > -rides (ENV, etc). > > On the upgrade they were ignored.
And this happens on every reboot? Colin, is there some way that systemd could come up, see nothing in /etc/systemd/system and then /etc/systemd/system gets put in place after? -Eric > ----- Original Message ----- > > From: "Eric Paris" <epa...@redhat.com> > > To: "Tim St Clair" <tstcl...@redhat.com> > > Cc: atomic-devel@projectatomic.io > > Sent: Thursday, May 21, 2015 3:08:28 PM > > Subject: Re: [atomic-devel] systemd.unit files and atomic upgrade. > > > > On Thu, 2015-05-21 at 16:07 -0400, Tim St Clair wrote: > > > Hey Folks - > > > > > > We recently upgraded our cluster 7.1.0->7.1.1->7.1.2 and we > > > uncovered that our systemd.unit files did not hold across > > > upgrades. > > > > > > Is/was this a known issue? > > > > You mean the files in /usr/lib/systemd/system changed? This is > > normal > > You mean the files in /etc/systemd/system changed? This is abnormal > > >
