Prev: "initrd" with command line parameters
Next: Interesting Article
From: Michael Black on 16 Apr 2008 23:44
On Wed, 16 Apr 2008, D Herring wrote:

> ahmedaden(a)gmail.com wrote:
>> Hi guys,
>>
>> I have noticed that /sbin/ldconfig runs at each boot and that it adds
>> a bit of time to the bootup process. I checked the man page but I
>> don't really understand what is happening.
>>
>> Does this have to be run at each bootup AND can someone give me a
>> description of what it does?
>
> Most programs use shared libraries (dlls in Windows-land). As a performance
> optimization, ldconfig searches the paths listed in /etc/ld.so.conf and makes
> a list of what it finds in /etc/ld.so.cache. Thus the linker doesn't have to
> search the paths each time a program loads.
>
> Really, ldconfig only needs to be called after installing a library into one
> of these paths. However, new users don't know to do that; but they have
> picked up this bad habit (who knows where) of rebooting whenever something
> doesn't work. Hence ldconfig (and a couple other caching programs) got added
> to the startup sequence.
>
That really answers the question as I interpret it. I didn't read it as
"what does it do" but "why does it need to run on every boot".

It hasn't bothered me, but since I thought I understood ldconfig, it
didn't really make sense that it ran on every boot.

Michael

> Look in /etc/rc.d for the startup scripts.
>
> - Daniel
>
From: buck on 17 Apr 2008 01:13
ahmedaden(a)gmail.com wrote in news:9a5f8ccc-dd4a-4c5a-a67e-71c246ac2c38
@u69g2000hse.googlegroups.com:

> Hi guys,
>
> I have noticed that /sbin/ldconfig runs at each boot and that it adds
> a bit of time to the bootup process.

If it is the time that bothers you, edit /etc/rc.d/rc.M and "background"
ldconfig. You do that by appending an ampersand at the end of the command,
like this:

/sbin/ldconfig &
or (as I do)
( /sbin/ldconfig ) &

rc.M will execute the next instruction immediately rather than waiting for
ldconfig to finish. If you're careful, there may be some other things in
the startup that would make the boot faster if backgrounded. Just don't
get carried away.
--
buck
From: "goarilla "kevin punt>paulus|" on 17 Apr 2008 16:54
Massimiliano Vessi wrote:
> ahmedaden(a)gmail.com il 19:46, mercoled� 16 aprile 2008 ha scritto:
>
>> Hi guys,
>>
>> I have noticed that /sbin/ldconfig runs at each boot and that it adds
>> a bit of time to the bootup process. I checked the man page but I
>> don't really understand what is happening.
>>
>> Does this have to be run at each bootup AND can someone give me a
>> description of what it does?
>>
>
> ldconfig check new libraries installed and wirte in al list to find easily
> to other program.
> If you prefer you can install anacron and perform this check every xx days.
> Max
>
whats wrong with crond or atd for that ?
From: Massimiliano Vessi on 17 Apr 2008 20:18

> Massimiliano Vessi wrote:
>> ahmedaden(a)gmail.com il 19:46, mercoled� 16 aprile 2008 ha scritto:
>>
>>> Hi guys,
>>>
>>> I have noticed that /sbin/ldconfig runs at each boot and that it adds
>>> a bit of time to the bootup process. I checked the man page but I
>>> don't really understand what is happening.
>>>
>>> Does this have to be run at each bootup AND can someone give me a
>>> description of what it does?
>>>
>>
>> ldconfig check new libraries installed and wirte in al list to find
>> easily to other program.
>> If you prefer you can install anacron and perform this check every xx
>> days. Max
>>
> whats wrong with crond or atd for that ?

Crond and atd are good for server, but not for desktop. Desktop usually
stays turned off the most part of the day.


From: Floyd L. Davidson on 17 Apr 2008 21:24
"goarilla <\"kevin<punt>paulus|\"@|skynet" <"punt> wrote:
>Massimiliano Vessi wrote:
>> ldconfig check new libraries installed and wirte in al
>> list to find easily
>> to other program.
>> If you prefer you can install anacron and perform this check every xx days.
>> Max
>>
>whats wrong with crond or atd for that ?

Just as unnecessary as anacron.

It only needs to be done when a new library is added.
It makes sense to have it done at boot time, but it
doesn't make a lick of sense to have it done
periodically on a running system. If a library is
added, the only sensible thing is to _immediately_ run
ldconfig to allow it to be accessed. There should never
be a time when a periodically invoked instance of
ldconfig would actually be useful...

--
Floyd L. Davidson <http://www.apaflo.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) floyd(a)apaflo.com
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: "initrd" with command line parameters
Next: Interesting Article