On Mon, May 23, 2016 at 4:01 PM, Florian Weimer wrote:
> I expect there are still installations out there which run /opt (or
> something like it) off NFS.
rpms shipped by many ISVs install things to /opt and also we seen
quite often that /opt has remote-fs mounted in it. Also,
administrators exp
On 05/23/2016 11:59 AM, Lennart Poettering wrote:
On Mon, 23.05.16 11:34, Florian Weimer (fwei...@redhat.com) wrote:
On 05/20/2016 04:10 PM, Lennart Poettering wrote:
If such systems require specialized unit files, then you can put
ldconfig.service there, instead of exposing all systemd users
On Mon, 23.05.16 12:12, Reindl Harald (h.rei...@thelounge.net) wrote:
> Am 23.05.2016 um 11:59 schrieb Lennart Poettering:
> >On Mon, 23.05.16 11:34, Florian Weimer (fwei...@redhat.com) wrote:
> >>I think the trigger is just implemented incorrectly. It should keep track
> >>of UUIDs in files (suc
Am 23.05.2016 um 11:59 schrieb Lennart Poettering:
On Mon, 23.05.16 11:34, Florian Weimer (fwei...@redhat.com) wrote:
I think the trigger is just implemented incorrectly. It should keep track
of UUIDs in files (such as /usr/.change-uuid), rather than looking at
mtimes. Then you can just writ
On Mon, 23.05.16 11:34, Florian Weimer (fwei...@redhat.com) wrote:
> On 05/20/2016 04:10 PM, Lennart Poettering wrote:
>
> >>If such systems require specialized unit files, then you can put
> >>ldconfig.service there, instead of exposing all systemd users to the
> >>service.
> >
> >No they don't.
On 05/20/2016 04:10 PM, Lennart Poettering wrote:
If such systems require specialized unit files, then you can put
ldconfig.service there, instead of exposing all systemd users to the
service.
No they don't. Basic Fedora works fine in this mode, without any
changes. It isn#t round, and it isn'
On Fri, 20.05.16 18:08, Ivan Shapovalov (inte...@intelfx.name) wrote:
> On 2016-05-20 at 14:59 +0200, Lennart Poettering wrote:
> > On Fri, 20.05.16 14:01, Florian Weimer (fwei...@redhat.com) wrote:
> >
> > > The default systemd configuration runs ldconfig at boot. Why?
> >
> > It's conditional
On Fri, 20.05.16 16:10, Lennart Poettering (lenn...@poettering.net) wrote:
> You mean, because not all local file systems have been mounted yet?
>
> So, there was actually a PR that tried to fix that, posted recently:
>
> https://github.com/systemd/systemd/pull/2859
>
> and it was merged re
On 05/20/2016 04:04 PM, Lennart Poettering wrote:
On Fri, 20.05.16 15:55, Florian Weimer (fwei...@redhat.com) wrote:
On 05/20/2016 02:59 PM, Lennart Poettering wrote:
On Fri, 20.05.16 14:01, Florian Weimer (fwei...@redhat.com) wrote:
The default systemd configuration runs ldconfig at boot.
On Fri, 20.05.16 16:06, Florian Weimer (fwei...@redhat.com) wrote:
> On 05/20/2016 04:04 PM, Lennart Poettering wrote:
> >On Fri, 20.05.16 15:55, Florian Weimer (fwei...@redhat.com) wrote:
> >
> >>On 05/20/2016 02:59 PM, Lennart Poettering wrote:
> >>>On Fri, 20.05.16 14:01, Florian Weimer (fwei..
On Fri, 20.05.16 15:55, Florian Weimer (fwei...@redhat.com) wrote:
> On 05/20/2016 02:59 PM, Lennart Poettering wrote:
> >On Fri, 20.05.16 14:01, Florian Weimer (fwei...@redhat.com) wrote:
> >
> >>The default systemd configuration runs ldconfig at boot. Why?
> >
> >It's conditionalized via Condit
On 05/20/2016 02:59 PM, Lennart Poettering wrote:
On Fri, 20.05.16 14:01, Florian Weimer (fwei...@redhat.com) wrote:
The default systemd configuration runs ldconfig at boot. Why?
It's conditionalized via ConditionNeedsUpdate=, which means it is only
run when /etc is older than /usr. (This is
On Fri, 20.05.16 14:01, Florian Weimer (fwei...@redhat.com) wrote:
> The default systemd configuration runs ldconfig at boot. Why?
It's conditionalized via ConditionNeedsUpdate=, which means it is only
run when /etc is older than /usr. (This is tested via checking
modification times of /etc/.upd
From what I understand, directories such as /usr/lib and stuff are
properly used even in case of a corrupted ld.so cache. like ldconfig
does not affect those directories at this time.
W dniu 20.05.2016 o 14:06, Vasiliy Tolstov pisze:
> 2016-05-20 15:01 GMT+03:00 Florian Weimer :
>> The default sys
2016-05-20 15:01 GMT+03:00 Florian Weimer :
> The default systemd configuration runs ldconfig at boot. Why?
>
> Most deployments of systemd appear to be dynamically linked, so if the ld.so
> caches are corrupted, you will never get to the point where you can run
> ldconfig.
>
> Running ldconfig to
15 matches
Mail list logo